| 1 |
"Walter Dnes" <waltdnes@××××××××.org> writes: |
| 2 |
|
| 3 |
> On Thu, Mar 29, 2012 at 10:26:22PM +1300, Kent Fredric wrote |
| 4 |
> |
| 5 |
>> Though of course, if anybody has custom stuff in say, /usr/portage/local/ |
| 6 |
>> which they make by hand, nuking /usr/portage will make you *Very* |
| 7 |
>> unpopular. |
| 8 |
> |
| 9 |
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#book_part3_chap5 |
| 10 |
> in the install handbook gives "/usr/local/portage" as an example overlay |
| 11 |
> directory. I thought it was implicit that one shouldn't edit or create |
| 12 |
> files in /usr/portage because they may be overwritten by the system e.g. |
| 13 |
> during an "emerge --sync". Maybe the manual needs to state this |
| 14 |
> explicitly. Also, /usr/local is the "standard" place to keep one's own |
| 15 |
> software and/or global customizations that aren't handled by the package |
| 16 |
> manager, but don't belong in one user's home directory. |
| 17 |
|
| 18 |
Where using /usr/portage/local is useful is for 'site local' |
| 19 |
packages. Where one system syncs externally and also has all of the |
| 20 |
locally generated/edited packages in /usr/portage/local, and the other |
| 21 |
systems share this site local repository simply by running "emerge |
| 22 |
--sync" to the 'master' system. |
Archives