From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [RFC] Inherit updates settings from master repositories by default
Date: Mon, 17 Feb 2014 03:09:05 -0500 [thread overview]
Message-ID: <36675111.3Q4er5RDo7@vapier> (raw)
In-Reply-To: <3237814.Ych0iObdgg@vapier>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
On Wednesday, February 05, 2014 03:03:10 Mike Frysinger wrote:
> On Saturday, February 01, 2014 20:38:05 Arfrever wrote:
> > If this attribute is not set explicitly, then it defaults to value of
> > 'masters' attribute.
>
> this i'm not so sure about. when you have a local overlay, portage
> complains when there are no masters which means most people have just
> blindly added "masters = gentoo". but if they have packages in there using
> the old name (on purpose), then updates will constantly tromp on that.
if portage is already processing updates from the main gentoo-x86 tree in
repos (that lack an updates/ dir) then i think it simplifies things to:
- if updates/ exists in the repo and the attribute is not explicitly set,
then default to "" instead of the value of "masters" and issue a warning
telling the user to explicit set the attribute
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-02-17 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 19:38 [gentoo-portage-dev] [RFC] Inherit updates settings from master repositories by default Arfrever Frehtes Taifersar Arahesis
2014-02-02 19:00 ` Sebastian Luther
2014-02-05 8:03 ` Mike Frysinger
2014-02-05 18:11 ` Sebastian Luther
2014-02-17 8:06 ` Mike Frysinger
2014-02-17 21:07 ` Sebastian Luther
2014-02-17 8:09 ` Mike Frysinger [this message]
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=36675111.3Q4er5RDo7@vapier \
--to=vapier@gentoo.org \
--cc=gentoo-portage-dev@lists.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