Gentoo Archives: gentoo-portage-dev

From: Ulrich Mueller <ulm@g.o>
To: gentoo-portage-dev@l.g.o
Cc: Zac Medico <zmedico@g.o>
Subject: Re: [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references (bug 378603)
Date: Mon, 06 Aug 2018 04:59:09
Message-Id: 23399.54678.259278.201017@a1i15.kph.uni-mainz.de
In Reply to: [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references (bug 378603) by Zac Medico
1 >>>>> On Sun, 5 Aug 2018, Zac Medico wrote:
2
3 > --- a/cnf/make.conf.example
4 > +++ b/cnf/make.conf.example
5 > [...]
6
7 > @@ -119,16 +119,16 @@
8 > # fetched on demand for a given build. If you would like to
9 > # selectively prune obsolete files from this directory, see
10 > # eclean from the gentoolkit package. Note that locations under
11 > -# /usr/portage are not necessarily safe for data storage. See the
12 > +# /var/db/repos/gentoo are not necessarily safe for data storage. See the
13 > # PORTDIR documentation for more information.
14 > -#DISTDIR=/usr/portage/distfiles
15 > +#DISTDIR=/var/db/repos/gentoo/distfiles
16
17 Shouldn't this be /var/cache/distfiles ...
18
19 > #
20 > # PKGDIR is the location of binary packages that you can have created
21 > # with '--buildpkg' or '-b' while emerging a package. This can get
22 > # up to several hundred megs, or even a few gigs. Note that
23 > -# locations under /usr/portage are not necessarily safe for data
24 > +# locations under /var/db/repos/gentoo are not necessarily safe for data
25 > # storage. See the PORTDIR documentation for more information.
26 > -#PKGDIR=/usr/portage/packages
27 > +#PKGDIR=/var/db/repos/gentoo/packages
28
29 ... and /var/cache/binpkgs?
30
31 > --- a/lib/portage/cache/flat_hash.py
32 > +++ b/lib/portage/cache/flat_hash.py
33 > @@ -144,7 +144,7 @@ class database(fs_template.FsBased):
34 > # Only recurse 1 deep, in order to avoid iteration over
35 > # entries from another nested cache instance. This can
36 > # happen if the user nests an overlay inside
37 > - # /usr/portage/local as in bug #302764.
38 > + # /var/db/repos/gentoo/local as in bug #302764.
39
40 Shouldn't a local overlay be in /var/db/repos/local, but never inside
41 of the gentoo repo?
42
43 > --- a/man/make.conf.5
44 > +++ b/man/make.conf.5
45 > @@ -219,10 +219,10 @@ Use the \fBPORTAGE_RO_DISTDIRS\fR variable to specify one or
46 > more read-only directories containing distfiles.
47 >
48 > Note
49 > -that locations under /usr/portage are not necessarily safe for data storage.
50 > +that locations under /var/db/repos/gentoo are not necessarily safe for data storage.
51
52 IMHO this statement should be made much stronger.
53
54 > See the \fBPORTDIR\fR documentation for more information.
55 > .br
56 > -Defaults to /usr/portage/distfiles.
57 > +Defaults to /var/db/repos/gentoo/distfiles.
58
59 /var/cache/distfiles
60
61 > @@ -800,10 +800,10 @@ to it's category. However, for backward compatibility with the layout
62 > used by older versions of portage, if the \fI${PKGDIR}/All\fR directory
63 > exists then all packages will be stored inside of it and symlinks to
64 > the packages will be created in the category subdirectories. Note
65 > -that locations under /usr/portage are not necessarily safe for data storage.
66 > +that locations under /var/db/repos/gentoo are not necessarily safe for data storage.
67
68 See above.
69
70 > See the \fBPORTDIR\fR documentation for more information.
71 > .br
72 > -Defaults to /usr/portage/packages.
73 > +Defaults to /var/db/repos/gentoo/packages.
74
75 /var/cache/binpkgs
76
77 > --- a/man/quickpkg.1
78 > +++ b/man/quickpkg.1
79 > @@ -17,7 +17,7 @@ modified since they were first installed.
80 > .br
81 > The packages, after being created, will be placed in \fBPKGDIR\fR.
82 > This variable is defined in \fBmake.conf\fR(5) and defaults to
83 > -/usr/portage/packages.
84 > +/var/db/repos/gentoo/packages.
85
86 See above.

Replies