1 |
On Wed, 2003-10-08 at 22:11, Brett I.Holcomb wrote: |
2 |
> I assume the ACCEPT_LICENSES goes in make.conf? If not where do I put it? |
3 |
|
4 |
Like all portage configuration, it goes in make.conf. We're pushing for |
5 |
having this more automated in portage itself. In fact, my original |
6 |
version of the function created a /usr/share/licenses directory and |
7 |
stored information there about which licenses had been accepted so the |
8 |
user would never be asked again. Then Mike (SpanKY) pointed out that |
9 |
ACCEPT_LICENSES was already a part of portage which just hadn't seen the |
10 |
light of day yet and would be perfect for this situation. |
11 |
|
12 |
> Thanks. |
13 |
> > On Wed, 2003-10-08 at 08:22, Dhruba Bandopadhyay wrote: |
14 |
> > > Hello |
15 |
> > > |
16 |
> > > From cvs changelogs I notice ID based based including ET are back in |
17 |
> > |
18 |
> > > -- What form does the licence check take exactly in theory to save me |
19 |
> > > having to re-emerge ET? Are ebuilds interactive for the first time ever |
20 |
> > > in the lifetime of the operating system? |
21 |
> > |
22 |
> > It checks the ACCEPT_LICENSES portage variable. If the current license |
23 |
> > (RTCW-ETEULA in this case) is not in your ACCEPT_LICENSES, then it |
24 |
> > displays the license and forces acceptance before unpacking. The build |
25 |
> > is only interactive if you have not specified to accept the license. At |
26 |
> > this time it does not add your acceptance to your ACCEPT_LICENSES |
27 |
> > variable for you, since we feel this is a function of portage itself |
28 |
> > (which is in the works) and not of the function. |
29 |
-- |
30 |
Chris Gianelloni |
31 |
Developer, Gentoo Linux |
32 |
Games Team |
33 |
|
34 |
Is your power animal a penguin? |