1 |
Alan McKinnon schrieb am 31.03.2009 21:37: |
2 |
> If I have identically named packages with the *same* version number in the |
3 |
> portage tree and in an overlay, how do I mask the overlay version without |
4 |
> deleting the overlay? |
5 |
> |
6 |
> I have kde-testing enabled to get koffice:2, but some packages conflict with |
7 |
> portage, like kscreensaver: |
8 |
> |
9 |
> [I] kde-base/kscreensaver |
10 |
> Available versions: |
11 |
> (3.5) 3.5.9 (~)3.5.10 |
12 |
> (4.2) (~)4.2.1 (~)4.2.1[1] [M](~)4.2.2[1] |
13 |
> |
14 |
> This one isn't too bad, but recently kdelibs did this and mixing overlay with |
15 |
> KDE is never a good idea. I can fiddle with PORTDIR_OVERLAY and |
16 |
> local/layman/make.conf but layman tends to undo my changes. |
17 |
> |
18 |
> So how can I mask just a specific ebuild from a specific overlay? |
19 |
> |
20 |
|
21 |
This is not possible with current portage. I think with paludis you can |
22 |
mask packages based on repositories, don't know about pkgcore though. |
23 |
|
24 |
You should be able to work around this by doing something like this in |
25 |
/etc/make.conf |
26 |
|
27 |
PORTDIR="/your/port/dir" |
28 |
PORTDIR_OVERLAY="/your/overlays $PORTDIR" |
29 |
|
30 |
This way portage prefers the the packages from the portage tree over |
31 |
packages with equal versions in overlays. |
32 |
|
33 |
-- |
34 |
Daniel Pielmeier |