public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: ebuild development (vpopmail, etc.)
Date: Mon, 18 Jul 2005 18:19:30 -0700	[thread overview]
Message-ID: <pan.2005.07.19.01.19.29.667464@cox.net> (raw)
In-Reply-To: 200507181813.28298.lists@seattleserver.com

Casey Allen Shobe posted <200507181813.28298.lists@seattleserver.com>,
excerpted below,  on Mon, 18 Jul 2005 18:13:28 +0000:

> 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.

Exactly.  The overlay is used first, if a copy exists there.

Of course, you'll need to re-digest the changed version, and anything in
FILESDIR it uses will need to be moved to the overlay FILESDIR, or an
attempted merge of the package with an overlay copy existing will fail,
(IOW, it will prefer the overlay copy and fail if the digest doesn't
match, even if a digest matching copy exists in the main portage tree),
but that should follow from the above.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-07-19  1:22 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
2005-07-19  1:19       ` Duncan [this message]
2005-07-18  5:14 ` 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=pan.2005.07.19.01.19.29.667464@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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