| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 20/12/12 10:37 AM, Brian Dolbec wrote: |
| 5 |
>> |
| 6 |
>>> /var/cache/repositories/ /var/cache/repositories/gentoo <== |
| 7 |
>>> the main portage tree /var/cache/repositories/local <== the |
| 8 |
>>> new location for a local overlay |
| 9 |
>>> /var/cache/repositories/some-overlay <== layman installed |
| 10 |
>>> overlay |
| 11 |
> |
| 12 |
> My idea for having all repos under one directory is to make it |
| 13 |
> easier for a pkg manager to simply scan the directory to know all |
| 14 |
> installed overlays. Currently each one has to be listed in a |
| 15 |
> configured variable in make.conf. So if you wanted your local |
| 16 |
> overlay somewhere else, then a symlink would work (provided the PM |
| 17 |
> can/will autoscan repos), or add it to the PORTDIR_OVERLAY variable |
| 18 |
> (current behavior). I don't otherwise have a strong desire for it |
| 19 |
> to be there. |
| 20 |
> |
| 21 |
> If and only if the tree and all overlays (not other directories) |
| 22 |
> are not under one directory, then an autoscan cannot easily |
| 23 |
> happen. |
| 24 |
> |
| 25 |
|
| 26 |
|
| 27 |
You could do this while not having the portage tree be in that |
| 28 |
directory. IE, portage goes in /var/cache/portage , and all the |
| 29 |
overlays go into /var/cache/repositories. |
| 30 |
|
| 31 |
The tree is separate enough IMO that autoscan can still happen easily, |
| 32 |
and also I believe that it can be assumed that the tree is in place. |
| 33 |
For instance, if the tree's location is defined to be elsewhere, it |
| 34 |
isn't done so via PORTDIR_OVERLAYS but rather PORTDIR. |
| 35 |
|
| 36 |
|
| 37 |
On an unrelated note, I would never treat my "local" overlays as |
| 38 |
cache. Ebuilds that (as a user) I wrote and installed by hand are not |
| 39 |
likely to be kept in a repository someplace, but rather the overlay |
| 40 |
dir would most likely be it's only location. IIRC the reason for |
| 41 |
/usr/portage/local/ was to have a path within the portage tree that |
| 42 |
rsync wouldn't kill; given that what you're suggesting is already not |
| 43 |
under the proposed portage tree location, emerge --sync couldn't touch |
| 44 |
it, and so I don't see a need at all to provide a 'local' repository |
| 45 |
destination by default. |
| 46 |
|
| 47 |
-----BEGIN PGP SIGNATURE----- |
| 48 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 49 |
|
| 50 |
iF4EAREIAAYFAlDTNlQACgkQ2ugaI38ACPCxQAEApT/7CaIbuVTwnDQk93hhDjGu |
| 51 |
mXKPdCJg4h1iMECtdoABAJj2601LuRPUKFJ+BJa/FqrdRTsjSpBRiEd8pvO2042P |
| 52 |
=W3T9 |
| 53 |
-----END PGP SIGNATURE----- |
Archives