1 |
<Quote who=bcowman@g.o> |
2 |
|
3 |
I did a work around for the sandboxing on ethereal 0.9.7, its now masked for |
4 |
testing using new arch testing keywords. I'm gonna close this out could u |
5 |
please resubmit me the correct kismet ebuild :). BTW here are the |
6 |
instructions for unmasking arch testing keywords: |
7 |
|
8 |
Another important snippet. If you want to unmask all ~x86 KEYWORDSed |
9 |
ebuilds, add the following to your /etc/make.conf: |
10 |
|
11 |
ACCEPT_KEYWORDS="~x86" |
12 |
|
13 |
ACCEPT_KEYWORDS is incremental like USE so it *will* keep the existing |
14 |
"x86" that is defined in your profile. This can also be done using the |
15 |
environment for temporary testing purposes: |
16 |
|
17 |
# export ACCEPT_KEYWORDS="~x86" (or "~ppc" or "~sparc", etc.) |
18 |
|
19 |
|
20 |
</Quote> |
21 |
|
22 |
Rigo |
23 |
|
24 |
|
25 |
On Sunday 13 October 2002 15:11, Rolf Offermanns wrote: |
26 |
> Can anyone help me with the following? |
27 |
> |
28 |
> When I do an emerge -s flex, I get |
29 |
> * sys-devel/flex |
30 |
> Latest version available: 2.5.4a-r4 |
31 |
> Latest version installed: 2.5.4a-r4 |
32 |
> Homepage: http://www.gnu.org/software/flex/flex.html |
33 |
> Description: GNU lexical analyser generator |
34 |
> |
35 |
> There is an -r5 ebuild in the portage dir. and this version is not masked, |
36 |
> so why isn't it listed in the search? |
37 |
> |
38 |
> Almost the same with the xfree-4.2.1.ebuild. This one is masked but if I |
39 |
> unmask it, I still get the 4.2.0-r12 version listed. |
40 |
> |
41 |
> When i try to give the 4.2.1 ebuild on the emerge command line I get the |
42 |
> following: |
43 |
> These are the packages that I would merge, in order. |
44 |
> |
45 |
> Calculating dependencies | |
46 |
> |
47 |
> emerge: all ebuilds that could satisfy ">=sys-devel/flex-2.5.4a-r5" (from |
48 |
> ebuild / x11-base/xfree-4.2.1 merge) have been masked. |
49 |
> |
50 |
> I am confused. What does that mean and where is it masked? |
51 |
> |
52 |
> -Rolf |