| 1 |
On Thursday 20 December 2012 13:36:27 Alan McKinnon wrote: |
| 2 |
> > What program uses this "local" directory? It's not used directly by |
| 3 |
> > portage itself, though portage has an exclude for it in the default |
| 4 |
> > PORTAGE_RSYNC_OPTS setting |
| 5 |
> > (in /usr/share/portage/config/make.globals). |
| 6 |
> |
| 7 |
> It goes back a long time, and is basically a poor man's local overlay |
| 8 |
> without having to use layman. As I understand it, portage will treat |
| 9 |
> the directory like any other when looking for ebuilds and resolving |
| 10 |
> deps, but exclude it from a sync. |
| 11 |
Nope, he means /usr/portage/local, not /usr/local/portage. It is rarely (if |
| 12 |
ever, nowadays) present, as I understand, but you can find it mentioned in |
| 13 |
that config file. It may be just a legacy definition by now, looking at how |
| 14 |
only layman was mentioned with relation to it and even that one appears not to |
| 15 |
use it any more. |
| 16 |
|
| 17 |
BTW, /usr/local/portage is hardly ""poor man's". Where are you going to store |
| 18 |
your local changes that are of interest only to you and not present in any |
| 19 |
other overlays? (like, you want to keep some old version of some package after |
| 20 |
it has been cleaned, or your personal mods). The location even accords to FHS, |
| 21 |
which is, apparently, a rarity :). |
| 22 |
|
| 23 |
George |
Archives