Gentoo Archives: gentoo-dev

From: "Rick \\\"Zero_Chaos\\\" Farina" <zerochaos@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Moving our/portage stuff to var
Date: Thu, 20 Dec 2012 16:26:04
Message-Id: 50D33BE5.9040301@gentoo.org
In Reply to: Re: [gentoo-dev] Moving our/portage stuff to var by Michael Mol
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 On 12/20/2012 11:16 AM, Michael Mol wrote:
5 > On Thu, Dec 20, 2012 at 11:01 AM, Ian Stakenvicius <axs@g.o> wrote:
6 > On 20/12/12 10:37 AM, Brian Dolbec wrote:
7 >>>>>
8 >>>>>> /var/cache/repositories/ /var/cache/repositories/gentoo <==
9 >>>>>> the main portage tree /var/cache/repositories/local <== the
10 >>>>>> new location for a local overlay
11 >>>>>> /var/cache/repositories/some-overlay <== layman installed
12 >>>>>> overlay
13 >>>>
14 >>>> My idea for having all repos under one directory is to make it
15 >>>> easier for a pkg manager to simply scan the directory to know all
16 >>>> installed overlays. Currently each one has to be listed in a
17 >>>> configured variable in make.conf. So if you wanted your local
18 >>>> overlay somewhere else, then a symlink would work (provided the PM
19 >>>> can/will autoscan repos), or add it to the PORTDIR_OVERLAY variable
20 >>>> (current behavior). I don't otherwise have a strong desire for it
21 >>>> to be there.
22 >>>>
23 >>>> If and only if the tree and all overlays (not other directories)
24 >>>> are not under one directory, then an autoscan cannot easily
25 >>>> happen.
26 >>>>
27 >
28 >
29 > You could do this while not having the portage tree be in that
30 > directory. IE, portage goes in /var/cache/portage , and all the
31 > overlays go into /var/cache/repositories.
32 >
33 > The tree is separate enough IMO that autoscan can still happen easily,
34 > and also I believe that it can be assumed that the tree is in place.
35 > For instance, if the tree's location is defined to be elsewhere, it
36 > isn't done so via PORTDIR_OVERLAYS but rather PORTDIR.
37 >
38 >
39 > On an unrelated note, I would never treat my "local" overlays as
40 > cache. Ebuilds that (as a user) I wrote and installed by hand are not
41 > likely to be kept in a repository someplace, but rather the overlay
42 > dir would most likely be it's only location. IIRC the reason for
43 > /usr/portage/local/ was to have a path within the portage tree that
44 > rsync wouldn't kill; given that what you're suggesting is already not
45 > under the proposed portage tree location, emerge --sync couldn't touch
46 > it, and so I don't see a need at all to provide a 'local' repository
47 > destination by default.
48 >
49 >>
50 >
51 > It's sounding like the nearly the optimal solution would be:
52 >
53 > /var/cache/portage/distfiles
54 > /var/cache/portage/repositories/gentoo
55 > /var/cache/portage/repositories/{sunrise,kde,gnome,whatever,layman,grabs}
56 > /var/db/portage/repositories/{non-cache,repo,names,go,here}
57
58 Not to oversimplify but why exactly can't we leave /usr/local/portage
59 where it is? I'm not going to want to cd
60 /var/db/portage/repositories/local every time I want to edit a local
61 ebuild...
62
63 - -ZC
64 >
65 > Clearly, some data in question needs to be treated as persistent, and
66 > others can be treated as cache. So it should probably be divided up
67 > that way. The placement of tree and overlays as subfolders of the same
68 > folder strikes me as appropriate, too.
69 >
70 > The only thing I can't see an elegant workaround for are how to avoid
71 > or handle repo name collisions between
72 > /var/cache/portage/repositories/* and /var/db/portage/repositories/*
73 >
74 > --
75 > :wq
76 >
77 >
78
79 -----BEGIN PGP SIGNATURE-----
80 Version: GnuPG v2.0.19 (GNU/Linux)
81 Comment: Using GnuPG with undefined - http://www.enigmail.net/
82
83 iQIcBAEBAgAGBQJQ0zvlAAoJEKXdFCfdEflKfiEP/0uLujqLlv1DVydqj3xXZUVq
84 t/c5mDsg3iJgt5T7Hm+ER949r2GUqju4veed4JQWFlVSaOoLEViL1Me/jPco5fC8
85 v064ktt2hOLPb+tR2IWaK3tR8i+LhcFEcIyANhl62ENPWgvOAR6V0KNFuudQLicS
86 QUFaJYKZkkYuPSTTqPld3QXzFwH1X6RCQaOtjCOqZKAZr9iW8HRNTTLpoa4bSMgr
87 VBswHyH+q0C9TzIVv5u8G8s8cYNdqHf1wrSTeMjq961tVzF3Tno5s1zk1MOyQ7cQ
88 MkQCxiMAum0d9PX87UkPuvHKgLdZ7e+tW26B9bS3M9yGu66lsHB7+sOTxFAJ9kqp
89 YKLuO2XPmpIMyDNc/5rQtTl5ygA9CmqSpUZEjMgwvCmemOHO3CsPXXQxfq6Ze7kK
90 /aNfCHJVEP/x8bY7PdWoexaScW/Qnqrqm6R+GCd6B3LGmTinGaDWYzJj+pAkpGUn
91 OAHcxATC9gX3AZr9atTFHRaPkD3L3FdYothVDZq5DDkW2qAmuhbqaEhzytDI3GLl
92 R+MEWYcMqvNLV5eYlNPe4OOaYfFTr/1mP0k/3ixjxJFwMDXxmIaJGTKoMOyoPu3O
93 diZlo0m2EPCH7Ggl9Fh0xf4P/wDSQB0AkfyldQhnVNbR5DRcTrkU6IfJBVLdcJ40
94 XljVqWuG27XmMXwjLGgV
95 =NLJg
96 -----END PGP SIGNATURE-----

Replies

Subject Author
Re: [gentoo-dev] Moving our/portage stuff to var Ian Stakenvicius <axs@g.o>