public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@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: Mon, 31 Mar 2008 14:15:45 +0400	[thread overview]
Message-ID: <1206958545.9865.41.camel@localhost> (raw)
In-Reply-To: <pan.2008.03.31.06.21.17@cox.net>

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


В Пнд, 31/03/2008 в 06:21 +0000, Duncan пишет:
> Mike Frysinger <vapier@gentoo.org> posted
> 200803302039.14615.vapier@gentoo.org, excerpted below, on  Sun, 30 Mar
> 2008 20:39:14 -0400:
> 
> > there is no package-manager specificness here.  it's already completely
> > doable from a user perspective, just having it in the ebuild makes my
> > life and users' lives easier.  i'm using it in packages that tend to
> > have a lot of extraneous patchsets associated with them.  the random
> > patches were punted from ebuilds and now it's up to the user to maintain
> > the feature sets.

> The point here though is that particularly for the glib patch, which has 
> undergone several rounds of testing and looks set for another round or 
> two at least, this user patch infrastructure would sure be nice!

It possible to use /etc/portage/bashrc to have this infrastructure.
Search mailing list, it was discussed here at least twice, and this is
example from solar:

http://dev.gentoo.org/~solar/bashrc
http://dev.gentoo.org/~solar/portage_misc/bashrc.autopatch

There is no need to put such things into ebuild.

-- 
Peter.

[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-03-31 10:20 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
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 [this message]
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=1206958545.9865.41.camel@localhost \
    --to=pva@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