| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Sat, 14 Jun 2008 11:53:51 +0200 |
| 3 |
> Luca Barbato <lu_zero@g.o> wrote: |
| 4 |
>> Ciaran McCreesh wrote: |
| 5 |
>>> On Sat, 14 Jun 2008 10:19:32 +0200 |
| 6 |
>>> Luca Barbato <lu_zero@g.o> wrote: |
| 7 |
>>>>> I'm confused. If I have a gcc-4.4.0.live ebuild which checks out |
| 8 |
>>>>> rev. 136737, after the merge do I have gcc-4.4.0_pre136737 |
| 9 |
>>>>> or gcc-4.4.0_pre1 (and gcc-4.4.0_pre2 next time I merge it, etc) |
| 10 |
>>>>> installed? |
| 11 |
>>>> it would be gcc-4.4.0_pre1 but you'll have the revision inside the |
| 12 |
>>>> ebuild as var so you can get it easily. (e.g. the description shows |
| 13 |
>>>> it) |
| 14 |
>>> And when would gcc-4.4.0_pre2 become available? |
| 15 |
>> It will be available once you trigger again the generation or if you |
| 16 |
>> put a normal ebuild with such name. |
| 17 |
> |
| 18 |
> And what triggers said generation? |
| 19 |
|
| 20 |
I already replied in this thread, I guess the information is getting too |
| 21 |
spread (and will be a pain put it back to the glep) =/ |
| 22 |
|
| 23 |
dev-zero pointed out that he would like to trigger the generation on a |
| 24 |
timely basis, I wanted to trigger it on the sync event, others had other |
| 25 |
opinion, so the best would be have it as separate phase and trigger it |
| 26 |
from the maint application. |
| 27 |
|
| 28 |
lu |
| 29 |
|
| 30 |
-- |
| 31 |
|
| 32 |
Luca Barbato |
| 33 |
Gentoo Council Member |
| 34 |
Gentoo/linux Gentoo/PPC |
| 35 |
http://dev.gentoo.org/~lu_zero |
| 36 |
|
| 37 |
-- |
| 38 |
gentoo-dev@l.g.o mailing list |
Archives