| 1 |
Neil Bothwick wrote: |
| 2 |
> On Thu, 13 Jun 2019 12:59:18 -0500, Dale wrote: |
| 3 |
> |
| 4 |
>> Neil Bothwick wrote: |
| 5 |
>>> You can set that in package.env too, I do this for Chromium: |
| 6 |
>>> |
| 7 |
>>> % cat /etc/portage/package.env/chromium |
| 8 |
>>> www-client/chromium alert-done.conf disk-tmpdir.conf j2.conf |
| 9 |
>>> |
| 10 |
>>> % cat /etc/portage/env/j2.conf |
| 11 |
>>> MAKEOPTS="-j2" |
| 12 |
>> Has that changed? I have a package.env FILE that contains a list of |
| 13 |
>> packages and the path to a file in /etc/portage/env/ that tells what to |
| 14 |
>> change that for package/ Looks like this: |
| 15 |
>> |
| 16 |
>> |
| 17 |
>> root@fireball / # cat /etc/portage/package.env/package.env |
| 18 |
>> #www-client/seamonkey ../env/single.conf |
| 19 |
>> #www-client/firefox ../env/single.conf |
| 20 |
>> #www-client/firefox ../env/notmpfs.conf |
| 21 |
>> #www-client/seamonkey ../env/notmpfs.conf |
| 22 |
>> app-office/libreoffice ../env/notmpfs.conf |
| 23 |
>> #sys-devel/gcc ../env/notmpfs.conf |
| 24 |
>> dev-qt/qtwebengine ../env/notmpfs.conf |
| 25 |
>> #dev-qt/qtwebkit ../env/notmpfs.conf |
| 26 |
>> #sci-electronics/kicad ../env/notmpfs.conf |
| 27 |
>> |
| 28 |
>> root@fireball / # ls -al /etc/portage/env/ |
| 29 |
>> total 16 |
| 30 |
>> drwxr-xr-x 2 root root 4096 Sep 3 2017 . |
| 31 |
>> drwxr-xr-x 14 root root 4096 May 31 00:40 .. |
| 32 |
>> -rw-r--r-- 1 root root 35 Sep 3 2017 notmpfs.conf |
| 33 |
>> -rw-r--r-- 1 root root 31 Feb 12 2017 single.conf |
| 34 |
>> |
| 35 |
>> root@fireball / # cat /etc/portage/env/notmpfs.conf |
| 36 |
>> PORTAGE_TMPDIR="/var/tmp/notmpfs" |
| 37 |
>> |
| 38 |
>> root@fireball / # cat /etc/portage/env/single.conf |
| 39 |
>> #EMERGE_DEFAULT_OPTS="-j1" |
| 40 |
>> |
| 41 |
>> root@fireball / # |
| 42 |
>> |
| 43 |
>> |
| 44 |
>> I think I'm doing this different than what you posted. It works but is |
| 45 |
>> it being changed and I need to update before it stops working? |
| 46 |
> The only difference is the way you are specifying the paths. Portage |
| 47 |
> looks in /etc/portage/env for these anyway, you are telling it to |
| 48 |
> load /etc/portage/env../env/whatever.conf, which is the same thing. |
| 49 |
> |
| 50 |
> |
| 51 |
|
| 52 |
|
| 53 |
OK. If something was changing, I wanted to update if needed. I sort of |
| 54 |
think your way is simpler tho. It took me a while to figure out how to |
| 55 |
make mine work. At the time, I couldn't find a lot of examples. |
| 56 |
|
| 57 |
Thanks for the info. |
| 58 |
|
| 59 |
Dale |
| 60 |
|
| 61 |
:-) :-) |
Archives