| 1 |
So perhaps they could be slotted as sys-kernel virtuals where 2.6 |
| 2 |
ebuilds have a "!( =gentoo-sources-2.4* )" DEPEND and 2.4 ebuilds have a |
| 3 |
"!( =gentoo-sources-2.6* )" DEPEND or something to that effect? Then you |
| 4 |
would not be forced to upgrade, unless you replaced the virtual by |
| 5 |
unmerging one kernel branch and merging the other. Would this work out? |
| 6 |
|
| 7 |
--My $0.02 |
| 8 |
|
| 9 |
Mike Frysinger wrote: |
| 10 |
> On Monday 23 August 2004 10:43 pm, Peter Gordon wrote: |
| 11 |
> |
| 12 |
>>Couldn't we just use different ebuild versions? |
| 13 |
>> |
| 14 |
>># emerge ">=gentoo-sources-2.6" |
| 15 |
>># emerge "=gentoo-sources-2.4.27" |
| 16 |
>> |
| 17 |
>>Or something similar? Would that work? |
| 18 |
> |
| 19 |
> |
| 20 |
> it should be that way i think but currently (i believe, someone please prove |
| 21 |
> me wrong) if you have 'gentoo-sources-2.4.27' and 'gentoo-2.6', portage will |
| 22 |
> automatically try to 'upgrade' you to 2.6 from 2.4.27 even if we SLOT them |
| 23 |
> differently |
| 24 |
> -mike |
| 25 |
|
| 26 |
-- |
| 27 |
() The ASCII Ribbon Campaign - against HTML Email, |
| 28 |
/\ vCards, and proprietary formats. |
| 29 |
--------------------------------------------------- |
| 30 |
Peter A. Gordon |
| 31 |
E-Mail: admin@×××××××××××××××××.com |
| 32 |
GPG Public Key ID: 0x109DBECE |
| 33 |
GPG Key Fingerprint (SHA1): |
| 34 |
E485 E2F7 11CE F9B2 E3D9 C95D 208F B732 109D BECE |
| 35 |
--------------------------------------------------- |
| 36 |
I digitally sign (using GnuPG) every email I write. |
| 37 |
If this or any other email that you recieve from me |
| 38 |
is not signed, or has a bad OpenPGP signature, |
| 39 |
please notify me. Thank you. --Peter |
| 40 |
--------------------------------------------------- |
Archives