1 |
Am Mo, 2003-06-09 um 23.28 schrieb Daniel Armyr: |
2 |
> Have you looked into the PORTAGE_OVERLAY setting in /etc/make.conf. It is my experience that an ebuild with the same version in the overlay dir will override the one in /usr/portage. So when I want to use an unstable package, I copy it to the overlay, and edit the KEYWORDS variable in the ebuild. A bit hacky, but it works. |
3 |
> --Daniel Armyr |
4 |
|
5 |
In gentoo forums I've found this: |
6 |
|
7 |
If you are using Portage >= 2.0.48, there is another option for |
8 |
installing masked packages that does not require editing package.mask. |
9 |
You can add a category/package entry into the file |
10 |
/etc/portage/package.unmask, which will survive across an "emerge sync". |
11 |
|
12 |
[http://forums.gentoo.org/viewtopic.php?t=33534] |
13 |
|
14 |
I've tried it, but it didn't show any effect. Currently this file just |
15 |
consists of |
16 |
|
17 |
sys-devel/gcc-3.3 |
18 |
|
19 |
What else should be in there? Will this file be loaded every time I |
20 |
emerge something, or do I have to regen something? Best regards, |
21 |
|
22 |
- Christian |
23 |
|
24 |
-- |
25 |
|
26 |
Christian Aust |
27 |
mailto:christian@××××××××××.de |
28 |
icq: 84500990 - Yahoo!: datenimperator - MSN: datenimperator |
29 |
GPG: 3C89AD72 |
30 |
|
31 |
|
32 |
|
33 |
-- |
34 |
gentoo-dev@g.o mailing list |