From: Casey Allen Shobe <lists@seattleserver.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ebuild development (vpopmail, etc.)
Date: Mon, 18 Jul 2005 18:13:28 +0000 [thread overview]
Message-ID: <200507181813.28298.lists@seattleserver.com> (raw)
In-Reply-To: <1121669825.10247.20.camel@supernova.lan.local>
On Monday 18 July 2005 06:57, Donnie Berkholz wrote:
> On Sun, 2005-07-17 at 22:07 -0700, Anthony Gorecki wrote:
> > On Sunday, July 17, 2005 9:26 pm, Casey Allen Shobe wrote:
> > > I'm also a bit confused about the portdir_overlay thing - If
> > > there exists a -r15, do I then add a -r16 to make emerge
> > > realize an update is available. What happens then when an
> > > -r16 hits the regular portage tree?
> >
> > Nothing at all. If there's a conflict between the standard tree
> > and your overlay, the ebuild in the overlay takes priority.
>
> In other words, something very important: You miss all the
> potentially critical changes contained in the new "official"
> revision.
So if I read correctly, when using an overlay, just don't change the
version number - a rebuild will be sufficient to use the overlay
version. Righto.
Cheers,
--
Casey Allen Shobe | http://casey.shobe.info
cshobe@seattleserver.com | cell 425-443-4653
AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523
SeattleServer.com, Inc. | http://www.seattleserver.com
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-18 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 4:26 [gentoo-dev] ebuild development (vpopmail, etc.) Casey Allen Shobe
2005-07-18 5:07 ` Anthony Gorecki
2005-07-18 6:57 ` Donnie Berkholz
2005-07-18 7:13 ` Anthony Gorecki
2005-07-18 7:25 ` Georgi Georgiev
2005-07-18 18:13 ` Casey Allen Shobe [this message]
2005-07-19 1:19 ` [gentoo-dev] " Duncan
2005-07-18 5:14 ` [gentoo-dev] " Alin Nastac
2005-07-18 13:19 ` Chris Gianelloni
2005-07-18 18:19 ` Casey Allen Shobe
2005-07-18 18:27 ` Jonathan Smith
2005-07-18 19:46 ` Chris Gianelloni
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=200507181813.28298.lists@seattleserver.com \
--to=lists@seattleserver.com \
--cc=gentoo-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