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