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