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: [gentoo-commits] gentoo-x86 commit in sys-apps/iproute2: ChangeLog iproute2-2.6.24.20080108.ebuild
Date: Mon, 31 Mar 2008 06:21:18 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.03.31.06.21.17@cox.net> (raw)
In-Reply-To: 200803302039.14615.vapier@gentoo.org

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.

I've been working with upstream, various users, and Dan Rahn from 
OpenSuSE (who has been absolutely great to work with, especially so since 
he can do the coding I can't), on glib-2.16 and gcc-4.3 compatibility 
patches for net-nntp/pan, and something like this would certainly make my 
life a lot easier.  FWIW the Gentoo bugs are 21160 and 214446, with half 
the story on the pan-user list (which is developer oriented too right now 
since the stable build is ancient so most users are on the beta releases 
or SVN).

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!

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

-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-31  6:21 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 [this message]
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=pan.2008.03.31.06.21.17@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