public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>, gentoo-portage-dev@lists.gentoo.org
Cc: Zac Medico <zmedico@gentoo.org>
Subject: Re: [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references (bug 378603)
Date: Sun, 5 Aug 2018 22:46:58 -0700	[thread overview]
Message-ID: <a9bd66d6-cb14-4e04-7227-7267eb12f829@gentoo.org> (raw)
In-Reply-To: <23399.54678.259278.201017@a1i15.kph.uni-mainz.de>


[-- Attachment #1.1: Type: text/plain, Size: 2820 bytes --]

On 08/05/2018 09:59 PM, Ulrich Mueller wrote:
>>>>>> On Sun, 5 Aug 2018, Zac Medico wrote:
> 
>> --- a/cnf/make.conf.example
>> +++ b/cnf/make.conf.example
>> [...]
> 
>> @@ -119,16 +119,16 @@
>>  #     fetched on demand for a given build. If you would like to
>>  #     selectively prune obsolete files from this directory, see
>>  #     eclean from the gentoolkit package. Note that locations under
>> -#     /usr/portage are not necessarily safe for data storage. See the
>> +#     /var/db/repos/gentoo are not necessarily safe for data storage. See the
>>  #     PORTDIR documentation for more information.
>> -#DISTDIR=/usr/portage/distfiles
>> +#DISTDIR=/var/db/repos/gentoo/distfiles
> 
> Shouldn't this be /var/cache/distfiles ...
> 
>>  #
>>  # PKGDIR is the location of binary packages that you can have created
>>  #     with '--buildpkg' or '-b' while emerging a package. This can get
>>  #     up to several hundred megs, or even a few gigs. Note that
>> -#     locations under /usr/portage are not necessarily safe for data
>> +#     locations under /var/db/repos/gentoo are not necessarily safe for data
>>  #     storage. See the PORTDIR documentation for more information.
>> -#PKGDIR=/usr/portage/packages
>> +#PKGDIR=/var/db/repos/gentoo/packages
> 
> ... and /var/cache/binpkgs?

Thanks, I've fixed the /var/cache/{distfiles,binpkgs} locations in v2.

>> --- a/lib/portage/cache/flat_hash.py
>> +++ b/lib/portage/cache/flat_hash.py
>> @@ -144,7 +144,7 @@ class database(fs_template.FsBased):
>>  					# Only recurse 1 deep, in order to avoid iteration over
>>  					# entries from another nested cache instance. This can
>>  					# happen if the user nests an overlay inside
>> -					# /usr/portage/local as in bug #302764.
>> +					# /var/db/repos/gentoo/local as in bug #302764.
> 
> Shouldn't a local overlay be in /var/db/repos/local, but never inside
> of the gentoo repo?

Yes, but for a long time /usr/local/portage was somewhat standard, in
fact it's still mentioned here:

https://wiki.gentoo.org/wiki/Custom_repository

Nowadays, repository verification will prevent that from working...

>> --- a/man/make.conf.5
>> +++ b/man/make.conf.5
>> @@ -219,10 +219,10 @@ Use the \fBPORTAGE_RO_DISTDIRS\fR variable to specify one or
>>  more read-only directories containing distfiles.
>>  
>>  Note
>> -that locations under /usr/portage are not necessarily safe for data storage.
>> +that locations under /var/db/repos/gentoo are not necessarily safe for data storage.
> 
> IMHO this statement should be made much stronger.

Yes, we could also say something about repository verification here. The
old defaults set a really bad example, so we needed statements like this
to steer people in the right direction.
--
Thanks,
Zac


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  reply	other threads:[~2018-08-06  5:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06  0:23 [gentoo-portage-dev] [PATCH 0/2] Change /usr/portage council approved locations (bug 378603) Zac Medico
2018-08-06  0:23 ` [gentoo-portage-dev] [PATCH 1/2] " Zac Medico
2018-08-06  0:23 ` [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references " Zac Medico
2018-08-06  4:59   ` Ulrich Mueller
2018-08-06  5:46     ` Zac Medico [this message]
2018-08-06  6:03       ` Zac Medico
2018-08-06  7:30       ` Brian Dolbec
2018-08-06 10:29         ` Ulrich Mueller
2018-08-06 18:35         ` Zac Medico
2018-08-06 21:50           ` M. J. Everitt
2018-08-06 22:39             ` Zac Medico
2018-08-06  5:32   ` [gentoo-portage-dev] [PATCH 2/2 v2] " Zac Medico
2018-08-06  7:44     ` Brian Dolbec
2018-08-06 18:46       ` Zac Medico
2019-04-18 17:03   ` [gentoo-portage-dev] [PATCH 2/2 v3] " Zac Medico
2019-04-18 17:28     ` Ulrich Mueller
2019-04-18 17:54       ` Zac Medico
2019-04-18 17:58   ` [gentoo-portage-dev] [PATCH 2/2 v4] " Zac Medico

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a9bd66d6-cb14-4e04-7227-7267eb12f829@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=ulm@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox