1 |
Ryan Hill schrieb: |
2 |
> On Sat, 14 Jun 2008 11:53:51 +0200 |
3 |
> Luca Barbato <lu_zero@g.o> wrote: |
4 |
> |
5 |
>> Ciaran McCreesh wrote: |
6 |
>>> On Sat, 14 Jun 2008 10:19:32 +0200 |
7 |
>>> Luca Barbato <lu_zero@g.o> wrote: |
8 |
>>>>> I'm confused. If I have a gcc-4.4.0.live ebuild which checks out |
9 |
>>>>> rev. 136737, after the merge do I have gcc-4.4.0_pre136737 |
10 |
>>>>> or gcc-4.4.0_pre1 (and gcc-4.4.0_pre2 next time I merge it, etc) |
11 |
>>>>> installed? |
12 |
>>>> it would be gcc-4.4.0_pre1 but you'll have the revision inside the |
13 |
>>>> ebuild as var so you can get it easily. (e.g. the description shows |
14 |
>>>> it) |
15 |
>>> And when would gcc-4.4.0_pre2 become available? |
16 |
>> It will be available once you trigger again the generation or if you |
17 |
>> put a normal ebuild with such name. |
18 |
> |
19 |
> So every user will have a different _preN version which would vary |
20 |
> depending on how often they rebuild the package and that has absolutely |
21 |
> no correlation with the revision number of the upstream codebase. I'm |
22 |
> sorry, but that's unacceptable. :/ |
23 |
> |
24 |
> If a user reports a bug in package-1.1_pre6, how do you determine what |
25 |
> revision he has installed? How can you even tell it's an scm ebuild? |
26 |
> If I want to report a bug I find to upstream, how to I know what |
27 |
> revision I have? Yes there are hacks like ESCM_LOGDIR, but they're |
28 |
> different for every SCM and you have to opt-in to use them. Most |
29 |
> people don't even know about them. |
30 |
No, the idea behind ESCM_LOGDIR was different. |
31 |
If you just want the revision of the current installed thing, you can |
32 |
grep through the environment. |
33 |
|
34 |
ESCM_LOGDIR mainly aimed to provide a history of revisions you |
35 |
installed. So that you can then tell upstream "Hey, I have this revision |
36 |
installed and it doesn't work, but this revision worked.". |
37 |
So it is definitely related, but not the same. |
38 |
-- |
39 |
gentoo-dev@l.g.o mailing list |