1 |
Thanks! |
2 |
|
3 |
On Fri, 2005-03-25 at 22:44 -0500, Robert Paskowitz wrote: |
4 |
> 1. Yes, just toss it in the spec file |
5 |
> 2. Yes, the dir should be on the host system. Catalyst will cp -a it |
6 |
> into the chroot. |
7 |
> |
8 |
> Robert |
9 |
> |
10 |
> James Dio wrote: |
11 |
> |
12 |
> >Thanks for the fast reply! two questions: |
13 |
> > 1. Where do I set it? in the spec file like |
14 |
> >portage_confdir: /root/confdir |
15 |
> > 2. This dir resides on the host system (so its not like i have to hack |
16 |
> >myway in and put the actual conf dir or anything? |
17 |
> > |
18 |
> > |
19 |
> >On Fri, 2005-03-25 at 22:03 -0500, Jeff Davidson wrote: |
20 |
> > |
21 |
> > |
22 |
> >>James Dio wrote: |
23 |
> >> |
24 |
> >> |
25 |
> >> |
26 |
> >>>Ok, I've built a wonderful cd and I'm not yet satisfied with it (as I |
27 |
> >>>wont be for a while) However I've run into where things are in testing |
28 |
> >>>(~x86) and blocked by package.mask. How do I get around this, I tried |
29 |
> >>>setting envscript=/root/catalyst-env.sh and in there i have a export |
30 |
> >>>ACCEPT_KEYWORDS="~x86" and It seems not not care. Any thoughts? and how |
31 |
> >>>do i get around the package.masked ones? (i wish there was a way to do |
32 |
> >>>this so i can see what is emerging X also but i guess i can wait for |
33 |
> >>>that) |
34 |
> >>> |
35 |
> >>>james |
36 |
> >>>(thanks for your help) |
37 |
> >>> |
38 |
> >>> |
39 |
> >>> |
40 |
> >>> |
41 |
> >>There's a portage_confdir setting for specfiles, point it to a directory |
42 |
> >>containing a package.keywords file with any entry you want in it. (You |
43 |
> >>can also use package.mask or any file from /etc/portage)/ |
44 |
> >> |
45 |
> >>-Monkey |
46 |
> >>-- |
47 |
> >>gentoo-catalyst@g.o mailing list |
48 |
> >> |
49 |
> >> |
50 |
> >> |
51 |
> >> |
52 |
> >> |
53 |
> |
54 |
> -- |
55 |
> gentoo-catalyst@g.o mailing list |
56 |
> |
57 |
> |
58 |
> |