public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fernando J. Pereda" <ferdy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Do not modify ebuilds which are already in the tree... even if masked
Date: Tue, 12 Jun 2007 12:16:31 +0200	[thread overview]
Message-ID: <20070612101631.GC4738@ferdyx.org> (raw)
In-Reply-To: <BD30C0AE-6488-40B4-9F0C-5417C92131D0@cilly.mine.nu>

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

On Tue, Jun 12, 2007 at 12:07:11PM +0200, cilly wrote:
>  Hi all,
> 
>  I think it is worth to discuss about `Do not modify ebuilds which are
>  already in the tree... even if masked.`
> 
>  Sometimes ebuilds which are already in the portage tree are modified
>  without changing the version-number, i.e. ebuild-r1 is in the portage
>  tree and the ebuild-r1 gets changed, i.e. useflag or other issues
>  without changing the version number to ebuild-r2. This causes
>  confusion i.e. in bug-reports.
> 
>  My opinion is not to change any ebuild which is in the portage tree,
>  even if the ebuild is masked.  I think the better way is to add an
>  ebuild with an updated version number, even if the ebuild is still
>  masked.
> 
>  I also recommend to manage hard-masked packages the same way, it
>  prevents confusion in bug-reports.
> 
>  What do you think?

I think this is also a bad idea. I seem to recall that this is
documented somewhere in the Developer Handbook...

- ferdy

-- 
Fernando J. Pereda Garcimartín
20BB BDC3 761A 4781 E6ED  ED0B 0A48 5B0C 60BD 28D4

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-12 10:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 10:07 [gentoo-dev] Do not modify ebuilds which are already in the tree... even if masked cilly
2007-06-12 10:16 ` Fernando J. Pereda [this message]
2007-06-12 10:20 ` Petteri Räty
2007-06-12 10:28   ` cilly
     [not found]     ` <200706121414.55040.carlo@gentoo.org>
2007-06-12 12:30       ` Sorry! WAS: " cilly
2007-06-12 10:21 ` Luca Barbato
2007-06-12 10:26   ` cilly
2007-06-12 10:55 ` Marius Mauch
2007-06-12 11:43   ` cilly
     [not found]     ` <20070612135602.25988df6@luna.home>
2007-06-12 12:01       ` [gentoo-dev] " cilly
2007-06-12 12:05       ` cilly
2007-06-12 12:17         ` Luca Barbato
2007-06-12 12:29           ` Markus Ullmann
     [not found]     ` <20070612135625.6e5a501a@loki>
2007-06-12 12:08       ` [gentoo-dev] " cilly
2007-06-13 12:50         ` [gentoo-dev] " Steve Long
2007-06-12 12:20     ` [gentoo-dev] " Michael Cummings
2007-06-12 11:50 ` Vlastimil Babka
2007-06-12 11:56   ` cilly
2007-06-12 12:05     ` [gentoo-dev] " Christian Faulhammer
2007-06-12 12:12       ` cilly
2007-06-12 12:37         ` Luca Barbato

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=20070612101631.GC4738@ferdyx.org \
    --to=ferdy@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