1 |
On Tue, 3 Oct 2017 11:13:31 -0700, Ian Zimmerman wrote: |
2 |
|
3 |
> > > When I'm thinking about installing a package, I can say |
4 |
> > > |
5 |
> > > USE='foo' emerge -p some-cat/some-package |
6 |
> > > |
7 |
> > > to see what would happen, without changing any /etc files. Is |
8 |
> > > there a similar way to specify a keyword override, without changing |
9 |
> > > /etc/portage/package.accept_keywords? Something along the lines of |
10 |
> > > |
11 |
> > > ACCEPT_KEYWORDS='<=some-cat/some-package-9999 ~amd64' \ |
12 |
> > > USE='foo' emerge -p some-cat/some-package |
13 |
> > |
14 |
> > ACCEPT_KEYWORDS="~amd64" emerge somepkg |
15 |
> |
16 |
> Thanks for the reply, I did learn something new from it. Nonetheless it |
17 |
> should be quite obvious that it does something different from what I was |
18 |
> "dreaming". |
19 |
|
20 |
You included the package atom on the env var, al la /etc/portage/package.* |
21 |
syntax, which you should have included only the setting. |
22 |
|
23 |
The trouble with setting this on the command line is that it will be |
24 |
changed on your next update. I prefer you have /etc/portage/package.* as |
25 |
directories, then I have a fail called temp in each that included the |
26 |
settings I am only trying out. When I have finished experimenting I can |
27 |
delete the file. |
28 |
|
29 |
|
30 |
-- |
31 |
Neil Bothwick |
32 |
|
33 |
"Do not handicap your children by making their lives easy." |
34 |
-- Robert Heinlein |