public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-apps/iproute2: ChangeLog iproute2-2.6.24.20080108.ebuild
Date: Sun, 30 Mar 2008 15:19:22 -0400	[thread overview]
Message-ID: <20080330191922.GA32327@aerie.halcy0n.com> (raw)
In-Reply-To: <20080330054051.GE24954@comet.had1.or.comcast.net>

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

Donnie Berkholz <dberkholz@gentoo.org> said:
> On 17:26 Sat 29 Mar     , Mike Frysinger (vapier) wrote:
> > 1.1                  sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild
> > 
> > file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild?rev=1.1&view=markup
> > plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-apps/iproute2/iproute2-2.6.24.20080108.ebuild?rev=1.1&content-type=text/plain
> 
> > 	local check base=${PORTAGE_CONFIGROOT}/etc/portage/patches
> > 	for check in {${CATEGORY}/${PF},${CATEGORY}/${P},${CATEGORY}/${PN}}; do
> > 		EPATCH_SOURCE=${base}/${CTARGET}/${check}
> > 		[[ -r ${EPATCH_SOURCE} ]] || EPATCH_SOURCE=${base}/${CHOST}/${check}
> > 		[[ -r ${EPATCH_SOURCE} ]] || EPATCH_SOURCE=${base}/${check}
> > 		if [[ -d ${EPATCH_SOURCE} ]] ; then
> > 			EPATCH_SUFFIX="patch"
> > 			EPATCH_FORCE="yes" \
> > 			EPATCH_MULTI_MSG="Applying user patches from ${EPATCH_SOURCE} ..." \
> > 			epatch
> > 			break
> > 		fi
> > 	done
> 
> This looks like it should be generic code somewhere else.

Actually, I'd say this should just be removed.  If a user wants to apply
a patch, they can put their own ebuild into an overlay and do it
themselves (presumably if they want to patch something, they'll know how
to make the simple modifications to an ebuild).  By allowing the user to
arbitrarily patch something means we have no idea what the user has
built and is filing a bug about.  If they installed an ebuild from an
overlay it is a lot easier to identify what they built.  Sure, they
could patch the ebuild in their tree, but by supporting user supplied
patches easily in this way, we are encouraging them to patch things
without our knowledge.  If we start supporting this across the board, I
can see bugs being filed when their patches break and they don't
understand what is happening.

Thanks,

-- 
Mark Loeser
email         -   halcy0n AT gentoo DOT org
email         -   mark AT halcy0n DOT com
web           -   http://www.halcy0n.com

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

  parent reply	other threads:[~2008-03-30 19:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Jfeop-0005oU-6S@stork.gentoo.org>
2008-03-30  5:40 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-apps/iproute2: ChangeLog iproute2-2.6.24.20080108.ebuild Donnie Berkholz
2008-03-30 16:13   ` Mike Frysinger
2008-03-30 19:19   ` Mark Loeser [this message]
2008-03-30 19:44     ` Mike Frysinger
2008-03-30 21:18       ` Mark Loeser
2008-03-30 21:42         ` Markus Ullmann
2008-03-30 21:46         ` Ciaran McCreesh
2008-03-30 21:57           ` Petteri Räty
2008-03-31  0:39         ` Mike Frysinger
2008-03-31  6:21           ` Duncan
2008-03-31 10:15             ` Peter Volkov
2008-03-31 18:04               ` Duncan
2008-03-31 15:37         ` User patches (Was: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-apps/iproute2: ChangeLog iproute2-2.6.24.20080108.ebuild) Vlastimil Babka
2008-03-31 19:26           ` Thomas de Grenier de Latour

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=20080330191922.GA32327@aerie.halcy0n.com \
    --to=halcy0n@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