1 |
On 07/24/2011 06:20 PM, Ulrich Mueller wrote: |
2 |
> Currently version 3.0 is only available with vanilla-sources and |
3 |
> gentoo-sources. Therefore the problem is that virtual/linux-sources-3 |
4 |
> would pull in one of these even for users of other *-sources (e.g. |
5 |
> hardened). |
6 |
> |
7 |
> On the other hand, allowing versions 3.* as dependency of |
8 |
> virtual/linux-sources-2.6 might be confusing. |
9 |
> |
10 |
> Therefore, my suggestion would be as follows: |
11 |
> 1. Temporarily change the dependency in virtual/linux-sources-2.6 |
12 |
> to >=2.6 in order to resolve the current issues with dependencies. |
13 |
> 2. Later, when most of *-sources are available in version 3.*, revert |
14 |
> linux-sources-2.6 to the current dependency and create |
15 |
> virtual/linux-sources-3. (I think the version should be just 3 and |
16 |
> not 3.0, unless you want a virtual for 3.0, 3.1, etc.) |
17 |
> |
18 |
> Or, a completely different approach: Drop the versioning of the |
19 |
> virtual altogether and have only virtual/linux-sources-0. (This might |
20 |
> cause some minor problems for users of 2.4 profiles, but I'd guess |
21 |
> that the remaining users are experienced enough to handle that.) |
22 |
Having separate versions for 2.6 and 3.0 doesn't make much sense. The |
23 |
are no 'incompatibilities' or major changes between 2.6 and 3 to justify |
24 |
a separate version/ebuild (unlike the 2.4 -> 2.6 transition). The only |
25 |
change is the version digits. |
26 |
|
27 |
I'd prefer the second solution. Could you be more specific about the |
28 |
problems that users of 2.4 profiles could encounter by that change? |
29 |
|
30 |
Thanks, |
31 |
|
32 |
-- |
33 |
Stratos Psomadakis |
34 |
<psomas@g.o> |