| 1 |
On 07/04/2011 02:10 AM, Matt Turner wrote: |
| 2 |
>>>> We use 2.0.6.916 on official releng releases. |
| 3 |
>>>> I tried 9999 on my private tests because [..] |
| 4 |
>>> |
| 5 |
>>> To me that leaves the question who uses 9999 for serious stuff at all. |
| 6 |
>>> In case it's no one (which we should find out) we could trash that |
| 7 |
>>> branch and fully concentrate on calalyst_2. |
| 8 |
>>> |
| 9 |
>>> I guess that sounds a bit radical at first. It doesn't have to be a |
| 10 |
>>> quick decision. Also, version control allows us to bring it back if needed. |
| 11 |
>>> |
| 12 |
>>> Ideas on find out who is using 9999: |
| 13 |
>>> |
| 14 |
>>> - Removing 9999 ebuild from the tree and see who's complaining |
| 15 |
>>> |
| 16 |
>>> - Resetting branch master to nothing but a README announcing |
| 17 |
>>> the possible death of that thread and a request to join |
| 18 |
>>> this mailing list and speak up about it if there is need. |
| 19 |
>>> |
| 20 |
>>> - Asking on one/some/all of gentoo-dev, gentoo-user, gentoo forums, |
| 21 |
>>> planet gentoo. |
| 22 |
>>> |
| 23 |
>>> After such action I imagine a time window of 2 to 4 weeks to give people |
| 24 |
>>> a chance to react. |
| 25 |
>>> |
| 26 |
>>> What do you think? |
| 27 |
>>> |
| 28 |
>>> |
| 29 |
>>>> I can confirm that the build with the master branch fails as it doesn't |
| 30 |
>>>> seem able to find the spec files or doesn't accept them - the official |
| 31 |
>>>> ones we use to build weekly releases. |
| 32 |
>>> |
| 33 |
>>> That seems to further decrease the chance that someone is using 9999 for |
| 34 |
>>> real to me. |
| 35 |
>> |
| 36 |
>> One week has passed by. Anyone? |
| 37 |
> |
| 38 |
> I'm perfectly fine with the change, especially after the graphviz |
| 39 |
> dependency of asciidoc was made optional. |
| 40 |
|
| 41 |
Please re-read the text above. It's not about asciidoc. |
| 42 |
I'll make a new thread. |
| 43 |
|
| 44 |
Best, |
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
Sebastian |
Archives