1 |
This section is snipped one of Allen M. posts on the monster gentoo |
2 |
health thread (last paragraph is where my topic starts: |
3 |
[...] |
4 |
Archive a portage tree by all means. But if an ebuild is removed that a |
5 |
user want to keep, the solution is so simple it's amazing. Copy the |
6 |
ebuild to /usr/local/portage in the correct directory structure. I |
7 |
maintain my own enlightenment-17 ebuilds, so to start I did this: |
8 |
|
9 |
mkdir -p /usr/local/portage/x11-wm |
10 |
cp -ar /usr/portage/x11-wm/e /usr/local/portage/x11-wm |
11 |
|
12 |
Run emerge. Simple as that. You might need to add an entry to |
13 |
package.mask so that portage won't use later versions in the main tree |
14 |
but that's all part of normal gentoo usage anyway. |
15 |
[...] |
16 |
|
17 |
In the event user runs with ~ARCHITECTURE flag set then masking won't |
18 |
do it... right? |
19 |
|
20 |
So my understanding is that user needs to set something in: |
21 |
/etc/portage/profile/package.provided showing an equal or higher |
22 |
version number than what is available in portage (masked or not). |
23 |
(To maintain users own package) |
24 |
|
25 |
Assuming I got this much right, is there a better way? |
26 |
|
27 |
I ask because setting a higher version number might eventually need |
28 |
bumping still higher... or if versioning changes somehow will `higher' |
29 |
not be noticed. |
30 |
|
31 |
Looking for a way not to have to check package.provided to make sure |
32 |
versioning is still good. |
33 |
|
34 |
-- |
35 |
gentoo-user@g.o mailing list |