public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Luther <SebastianLuther@gmx.de>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] Implement --newrepo flag.
Date: Tue, 18 Feb 2014 18:35:38 +0100	[thread overview]
Message-ID: <530399EA.6020702@gmx.de> (raw)
In-Reply-To: <CAGNm6ezEFwRXgCGkC9Usk67-b+ULFGnaYT9Lb2sSYcs3A5M5Gg@mail.gmail.com>

Am 17.02.2014 22:44, schrieb David James:


> From a theoretical perspective, the reason why I implemented this is
> because "ebuilds" are the source of truth. According to the ebuilds, the
> owner repo of dev-libs/C-1 is repo1, so this means that, with --newrepo,
> any binpkg for dev-libs/C-1 from repo2 would be invalid.

Actually this test passes even without --new-repo. So yes, your
interpretation is what's used by portage. Patch is committed.

> 
> This functionality is useful in the case where an ebuild changes repos.
> In this case, with --newrepo, you would want the package to be rebuilt
> and any binaries to be invalidated, and our tests validate this.
> 
> Cheers,
> 
> David
> 



  reply	other threads:[~2014-02-18 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 17:31 [gentoo-portage-dev] [PATCH] Implement --newrepo flag David James
2014-02-14 20:31 ` Sebastian Luther
2014-02-14 20:43   ` David James
2014-02-14 21:37     ` Sebastian Luther
2014-02-17  4:57       ` David James
2014-02-17  7:49         ` Mike Frysinger
2014-02-17 16:39           ` Brian Dolbec
2014-02-17 17:52             ` David James
2014-02-17 20:09               ` Sebastian Luther
2014-02-17 21:44                 ` David James
2014-02-18 17:35                   ` Sebastian Luther [this message]
2014-02-17 18:23             ` Sebastian Luther
2014-02-17  7:45 ` Mike Frysinger

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=530399EA.6020702@gmx.de \
    --to=sebastianluther@gmx.de \
    --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