Ciaran McCreesh wrote:
On Sat, 14 Jun 2008 11:53:51 +0200
Luca Barbato <[EMAIL PROTECTED]> wrote:
Ciaran McCreesh wrote:
On Sat, 14 Jun 2008 10:19:32 +0200
Luca Barbato <[EMAIL PROTECTED]> wrote:
I'm confused. If I have a gcc-4.4.0.live ebuild which checks out
rev. 136737, after the merge do I have gcc-4.4.0_pre136737
or gcc-4.4.0_pre1 (and gcc-4.4.0_pre2 next time I merge it, etc)
installed?
it would be gcc-4.4.0_pre1 but you'll have the revision inside the
ebuild as var so you can get it easily. (e.g. the description shows
it)
And when would gcc-4.4.0_pre2 become available?
It will be available once you trigger again the generation or if you
put a normal ebuild with such name.
And what triggers said generation?
I already replied in this thread, I guess the information is getting too
spread (and will be a pain put it back to the glep) =/
dev-zero pointed out that he would like to trigger the generation on a
timely basis, I wanted to trigger it on the sync event, others had other
opinion, so the best would be have it as separate phase and trigger it
from the maint application.
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
gentoo-dev@lists.gentoo.org mailing list
