public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Emerge Ignores Newer Ebuilds If Older Given In Package.Provided
Date: Thu, 27 May 2010 08:20:17 -0400	[thread overview]
Message-ID: <4BFE6381.70509@libertytrek.org> (raw)
In-Reply-To: <20100526203512.2f9728d7.frank.peters@comcast.net>

On 2010-05-26 8:35 PM, Frank Peters wrote:
> There are some requests on bugs.gentoo.org that package.provided be 
> extended in various ways. In my opinion, package.provided should 
> accomplish just what the name implies. It should indicate that the
> Gentoo user has compiled his own version of an ebuild (for whatever
> reason) and if a newer ebuild exists, regardless of dependencies,
> this should be indicated to the user (as it is with a normally
> emerged ebuild).

Isn't that what your local overlay is for?

It sounds like you added a package that wasn't yet available in the main
gentoo repo, then later, an updated package became available in the main
gentoo repo, and you want that update to be applied?

That is what your local overlay is for - so you can add your own
packages, but updates from the main repo will still be available.



  parent reply	other threads:[~2010-05-27 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 19:08 [gentoo-amd64] Emerge Ignores Newer Ebuilds If Older Given In Package.Provided Frank Peters
2010-05-26 20:21 ` Kenneth Prugh
2010-05-26 22:27   ` Frank Peters
2010-05-26 23:25     ` Barry Schwartz
2010-05-27  0:35       ` Frank Peters
2010-05-27  1:25         ` Barry Schwartz
2010-05-27 12:20         ` Tanstaafl [this message]
2010-05-27 12:38         ` [gentoo-amd64] " Duncan

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=4BFE6381.70509@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --cc=gentoo-amd64@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