avsm changed the topic of #mirage to: mirage 2 released! party on!
brson has quit [Ping timeout: 276 seconds]
rgrinberg has quit [Ping timeout: 265 seconds]
rgrinberg has joined #mirage
abeaumont_ has quit [Ping timeout: 265 seconds]
beaumonta has joined #mirage
jermar has joined #mirage
rgrinberg has quit [Ping timeout: 260 seconds]
copy` has quit [Quit: Connection closed for inactivity]
nullcat has joined #mirage
insitu has joined #mirage
jermar has quit [Ping timeout: 276 seconds]
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
insitu has joined #mirage
balduin has quit [Ping timeout: 244 seconds]
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
insitu has joined #mirage
nullcat has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
jermar has joined #mirage
dezzy_ has joined #mirage
dezzy has quit [Ping timeout: 255 seconds]
mrutland_ is now known as mrutland
AltGr has joined #mirage
balduin has joined #mirage
yomimono_ has joined #mirage
agarwal1975 has joined #mirage
agarwal1975 has quit [Quit: agarwal1975]
agarwal1975 has joined #mirage
yomimono_ has quit [Ping timeout: 240 seconds]
copy` has joined #mirage
agarwal1975 has quit [Quit: agarwal1975]
agarwal1975 has joined #mirage
agarwal1975 has quit [Client Quit]
rgrinberg has joined #mirage
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jermar has quit [Ping timeout: 244 seconds]
srenatus[m] has quit [Remote host closed the connection]
yomimono_ has joined #mirage
<yomimono_>
anyone know how to find out which package versions the currently active https://mirage.io was built with?
<yomimono_>
I think it's built in travis so there's probably a build log somewhere, but not sure where to look
<Drup>
yomimono_: it would be nice to use app_info to generate a webpage like that ;)
<yomimono_>
drup: it would be nice to do a lot of things! file an issue? ;)
<yomimono_>
the stack is currently full and has no room for new items
<Drup>
ahah, yeah, I guess
<yomimono_>
in fact, items have been falling out of the bottom of the stack for some time. also out of the sides.
<yomimono_>
it's not a very good stack.
<yomimono_>
i'm not clear on how that would actually work -- could you self-serve it? I guess the library versions are configure-time information, so you could generate this and then include it in whatever storage you're using
<Drup>
Functoria.app_info is a device that generates an ocaml file that contains the list of packages names and their version
<Drup>
you just need to ... make a webpage out of it
<yomimono_>
yeah, then do the stuff I said, ok
<yomimono_>
or do something interesting with it with cohttp, I guess
<Drup>
well, you don't need to do any storage thing, it's already in an ocaml file, so it'll be compiled in.
miragebot has joined #mirage
<miragebot>
mirage/master dd4b7da Anil Madhavapeddy: doc: add a couple more libraries into the mix