public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Gaffney <agaffney@skylineaero.com>
To: Ciaran McCreesh <ciaranm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ebuild revisions
Date: Tue, 30 Dec 2003 08:46:27 -0600	[thread overview]
Message-ID: <3FF18FC3.50402@skylineaero.com> (raw)
In-Reply-To: <20031230144712.1c262e27@snowdrop.home>

Ciaran McCreesh wrote:
> On Tue, 30 Dec 2003 08:28:07 -0600 Andrew Gaffney
> <agaffney@skylineaero.com> wrote:
> | Whenever an ebuild goes from say -r1 to -r2, that is just a revision
> | of the ebuild, not the program itself, correct? If so, in most cases,
> | you will get the exact same code generated, correct? If the first one
> | works, what is the point of upgrading to the next revision to get the
> | exact same code?
> 
> Incorrect. A revision bump will only be done if the installed code is
> changed enough that the user should upgrade.
> 
> For example, if I added a minor compile fix to foo-1.0.ebuild, I
> wouldn't do a revision bump. However, if I added a security or
> functionality patch to foo-1.0.ebuild, or if I made significant changes
> to foo's configuration files, I *would* bump it to-r1.

Okay. That makes sense.

-- 
Andrew Gaffney


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-12-30 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 14:28 [gentoo-dev] ebuild revisions Andrew Gaffney
2003-12-30 14:47 ` Ciaran McCreesh
2003-12-30 14:46   ` Andrew Gaffney [this message]
2003-12-30 14:58 ` foser
2003-12-30 16:26 ` Brian Jackson

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=3FF18FC3.50402@skylineaero.com \
    --to=agaffney@skylineaero.com \
    --cc=ciaranm@gentoo.org \
    --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