<mato>
What's the current state of the behaviour of "mirage describe"? ISTR we decided that "--eval" should be the default if the project is configured.
<mato>
However, either it's not and/or --eval is broken. If I try it with latest master I don't see the actual (configured) values, just the defaults.
<mato>
yomimono: Any ideas? I forget which was the PR that this was last touched in.
<mato>
*With* a config.ml --version doesn't work either, just prints %%VERSION%%. I'll add a comment to the issue.
<hannes>
in the end, I had some code somewhere which did a better job on the config and recompilation, but this got lost during rebase etc.
<yomimono>
mato: that should be fixed automatically when we do a proper release, but comment is fine; we should check and make sure
<hannes>
the %%VERSION%% is a disjoint problem (namely the topkg watermarking does not apply for urls starting with git in repos, only for git pins and for releases)
<mato>
ok, comment added anyway
<mato>
Shall I raise a separate issue about the describe behaviour?
<yomimono>
which requests comment from hannesm, me, and samoht, but none of us have commented
<hannes>
(it should be a stopper for 3.0 final, but I guess not an issue for beta releases; though I'll try to rework my functoria config patches)
<mato>
ha :)
<mato>
ok, so I already made one, good :)
<mato>
perhaps add it to the relevan "for 3.0" list
<hannes>
since I never used describe, I'd rather be happy to hear what the behaviour should be
<mato>
well, I think we discussed that on the list
<mato>
I'll add a link to the thread to the issue
<hannes>
ah, right.
<mato>
AFAICT the conclusion was that in the presence of a config.ml it should eval the parameters, ie. reflect the configured values
<Drup>
mato: I remember implementing that. It doesn't work ?
<hannes>
Drup: mirage describe does not take the mirage configure configured parameters into account
<Drup>
huum, that's wrong, I remember painfully adding that.
<Drup>
hannes: are you going to take a look or should I ?
<hannes>
Drup: pls do if you have time. I'll be in transit again soon
<Drup>
ok
<mato>
Drup: doesnt seem to
<mato>
Drup: adding a comment and Cc to you on the issue
<hannes>
Drup: I have plans/unfinished patches to shuffle a bit of functoria_app around -- main target is: don't have arguments to build, don't compile config.ml during build (but instead reuse the config.cmxs)
rgrinberg has quit [Remote host closed the connection]
<mato>
Hmm.
<mato>
mirage configure --help used to work, did it not?
<hannes>
this will (hopefully) unbreak the version without a config.ml etc.
<mato>
(Not sure what these are called in english)
<yomimono>
this is a more specific class of thing than a woodburning fireplace, right? I think I read an article about them in some crunchy-granola publication I get
<yomimono>
they sounded warm and heavenly
<mato>
Yup. As opposed to a normal woodburner these accumulate much more heat and are generally left to constantly burn.
dinosaure has quit [Ping timeout: 248 seconds]
nathan7 has quit [Ping timeout: 265 seconds]
nathan7 has joined #mirage
andreas23 has quit [Quit: Leaving.]
<reynir>
I think I've heard of these. Are they called banya in russian?
mort___ has quit [Ping timeout: 240 seconds]
<mato>
reynir: No idea, I lived elsewhere as a child, didn't have Russian at school.
mort___ has joined #mirage
<mato>
reynir: But yeah, they probably have the same or similar kind of thing.
insitu has joined #mirage
mort___1 has joined #mirage
<reynir>
The place where I was staying the last two weeks had this coal-fired oven http://imgur.com/a/hw2Ll
<reynir>
it's about 2 meters tall. Can't sleep on it though
<yomimono>
although apparently you can store cardboard boxes on it???
<yomimono>
it's clear that this must be venting somewhere else but it still makes me nervous
<reynir>
heh
<reynir>
I think the vent is about the height of the upper opening
<reynir>
but the oven has quite a lot of mass
<reynir>
it doesn't get burning hot on the outside
mort___ has quit [Ping timeout: 240 seconds]
<reynir>
the warmest place on the outside seemed to be a bit below the upper lid :-)
abeaumont has quit [Remote host closed the connection]
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<mort___>
trying to track down an opam install oddity — not picking up consistent package dependency versions between local OSX install and travis. anyone available who's OPAM-fu is strong? ('cos mine ain't)
<mort___>
@Drup: this relates to the problems I was having getting Travis to pick up the latest Tyxml...
<Drup>
link to the various files ?
<mort___>
will create some gists. summary is: travis build of mirage-decks fails because OPAM prefers to install tyxml.3.2.1 rather than tyxml.4.0.1. works just fine on my local install in a fresh 4.03 aliased switch.
<mort___>
diffing the packages selected for install indicates that, for some reason i can't fathom, travis wants to install tyxml.3.2.1 and oasis.0.4.8 while my local install wants to install oasis.0.4.7 and tyxml.4.0.1
<Drup>
(there was talks about picking the lowest version in CI on purpose to force version to add constraints, not sure if it was actually done, it was mostly a joke :p)
<Drup>
force people*
<mort___>
aha. aha. ahahaha.
<Drup>
(Note that adding constraints is better handled by mirage 3)
<mort___>
fwiw using the string "tyxml>=4.0.0" in the packages list appears to be doing the right thing :)
<mort___>
(maybe)
<mort___>
ok, have pushed that to travis. let's see what it says now. thanks!
mort___ has quit [Quit: Leaving.]
AltGr has quit [Ping timeout: 240 seconds]
AltGr has joined #mirage
AltGr has quit [Ping timeout: 246 seconds]
AltGr has joined #mirage
AltGr has quit [Ping timeout: 245 seconds]
demonimin has quit [Ping timeout: 248 seconds]
demonimin has joined #mirage
demonimin has joined #mirage
demonimin has quit [Changing host]
smondet has joined #mirage
andreas23 has joined #mirage
mort___ has joined #mirage
insitu has joined #mirage
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]