1 |
On Tuesday, September 01, 2015 4:02:52 AM Walter Dnes wrote: |
2 |
> How many heads will explode? I have /etc/portage/package.use/package.use |
3 |
> file (YES!) The only reason I made a package.use directory was because I |
4 |
> set up a cross-build environment, so that my ancient 32-bit Atom netbook |
5 |
> wouldn't have to spend 14 hours building Seamonkey. The cross-compiler |
6 |
> *DEMANDS* a package.use directory. |
7 |
> |
8 |
> [d531][waltdnes][~] ll /etc/portage/package.use/ |
9 |
> total 24 |
10 |
> drwxr-xr-x 2 root root 4096 Jul 30 17:05 . |
11 |
> drwxr-xr-x 13 root root 4096 Jul 30 17:03 .. |
12 |
> -rw-r--r-- 1 root root 41 Mar 25 00:04 cross---help |
13 |
> -rw-r--r-- 1 root root 37 Mar 25 00:01 cross--p |
14 |
> -rw-r--r-- 1 root root 274 May 4 12:07 cross-i686-pc-linux-gnu |
15 |
> -rw-r--r-- 1 root root 585 Jul 30 17:05 package.use |
16 |
> |
17 |
> |
18 |
|
19 |
Mine looks similar. The reason it demands a directory is because it owns those |
20 |
files and will make changes to them during the build stages. If you want to |
21 |
make changes to the cross compiler use flags you need to make them on your own |
22 |
package.use or some other file or it will overwrite them. |
23 |
|
24 |
Also one exception to the directory naming convention is the keywords file. The |
25 |
file was package.accept_keywords but the directory is package.keywords. IIRC |
26 |
crossdev just created that one and portage used both except for autounmask |
27 |
that kept wanting to write to the cross-* files until I moved that file. I |
28 |
always tought autounmask would write to the original package.* filename (since |
29 |
cross-* comes before package.*) until I saw Alan's reply. |
30 |
|
31 |
-- |
32 |
Fernando Rodriguez |