| 1 |
On Sunday 10 October 2004 10:19, Daniel Drake wrote: |
| 2 |
> To use an example, we plan to make gentoo-patched 2.4 and 2.6 kernels |
| 3 |
> available under "gentoo-sources" (currently they are split into 2 |
| 4 |
> packages). |
| 5 |
> |
| 6 |
> The problem is that a 2.4 user would see 2.6 as a package update, even |
| 7 |
> though they might really want to stick to 2.4. We could get around this by |
| 8 |
> having say 2.4 as stable, 2.6 as ~arch, but that makes it not possible to |
| 9 |
> release "testing" releases for kernels. |
| 10 |
> |
| 11 |
> So, we'd like a way to allow users to say "I want to stick to 2.4 for |
| 12 |
> kernel packages" or something like that. But I don't think this is limited |
| 13 |
> to kernels, I think this might be useful in other areas of the tree too? |
| 14 |
|
| 15 |
How about extending the profiles? Especially easy with cascading profiles... |
| 16 |
|
| 17 |
> Take GTK+ (2.4 - the stable branch) as an example. New GTK+ releases first |
| 18 |
> come into ~arch for a few weeks, then get moved into stable. I develop GTK+ |
| 19 |
> apps, so I use package.keywords to "unmask" these packages. |
| 20 |
> If the gentoo maintainers decided to put ebuilds for the 2.5 (development) |
| 21 |
> branch into the tree, then I'd be asked to upgrade. But thats not what I |
| 22 |
> want, not many people like developing for a moving-target API. |
| 23 |
> |
| 24 |
> So, are there any plans for some sort of slot selection mechanism? One |
| 25 |
> thing that I have thought of is some sort of portage application used to do |
| 26 |
> this. Something like: |
| 27 |
> |
| 28 |
> version-select gtk+ 2.4 |
| 29 |
|
| 30 |
Profile files and /etc/portage files do all of this already. |
| 31 |
|
| 32 |
Regards, |
| 33 |
Jason Stubbs |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-portage-dev@g.o mailing list |
Archives