| 1 |
On Wednesday 20 November 2002 4:21 pm, Chad Huneycutt wrote: |
| 2 |
|
| 3 |
> Use profiles for this. The process would go something like this: |
| 4 |
> |
| 5 |
> 1. Install Gentoo on your dev box |
| 6 |
> 2. Tweak until the stability is where you want it (i.e., find stable |
| 7 |
> versions of software, make patches -- and submit them to bugzilla, and |
| 8 |
> place any outside ebuilds in /usr/local/portage or whatever and set |
| 9 |
> PORTAGE_OVERLAY -- or whatever the var is) |
| 10 |
> 3. Once you have the packages from portage like you want them, create a |
| 11 |
> new profile: |
| 12 |
> # cd /usr/portage/profiles |
| 13 |
> # cp -r your_current_profile my_stable_profile |
| 14 |
> # mv my_stable_profile /usr/local/portage/profiles |
| 15 |
> # rm /etc/make.profile |
| 16 |
> # ln -s /usr/local/portage/profiles/my_stable_profile /etc/make.profile |
| 17 |
> # cd /usr/local/portage/profiles/my_stable_profile |
| 18 |
> # echo "all_my_package-revisions" > packages |
| 19 |
> |
| 20 |
> The packages file is well commented, but basically you can use it to |
| 21 |
> "pin" the versions of all your packages (or just the ones that matter). |
| 22 |
> 4. Now you should be able to use that profile directory as |
| 23 |
> /etc/make.profile on all your systems. |
| 24 |
|
| 25 |
Im sure that wouldnt work. Your profile would refer to your chosen version, |
| 26 |
but that doesnt help when the ebuild (and other files) for that version is |
| 27 |
removed from portage. |
| 28 |
|
| 29 |
I agree with you that this *should* work. That means that old revisions would |
| 30 |
never be removed from portage. |
| 31 |
|
| 32 |
But they are, so it doesnt :-( |
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-dev@g.o mailing list |
Archives