Re: from / to /usr/: a summary
- To: firstname.lastname@example.org
- Subject: Re: from / to /usr/: a summary
- From: "Bernhard R. Link" <email@example.com>
- Date: Sun, 1 Jan 2012 12:57:56 +0100
- Message-id: <[🔎] 20120101115756.GB3185@server.brlink.eu>
- Mail-followup-to: firstname.lastname@example.org
- In-reply-to: <email@example.com>
- References: <20111230013640.GA4475@leaf> <20111230T123451.GA.firstname.lastname@example.org> <20111230114813.GA15138@bongo.bofh.it> <4EFDBB33.email@example.com> <20111230134737.GA17748@bongo.bofh.it> <20111230135821.GA2167@angband.pl> <20111231025922.GD30223@mailgate.onlinehome-server.info> <CANVYNa92t4N5zrWm=UX=PO1f19X=YkQvYB9sZDO1cQ7bHrKroA@mail.gmail.com> <20111231092302.GA2200@server.brlink.eu> <firstname.lastname@example.org>
* Russ Allbery <email@example.com> [111231 18:41]:
> "Bernhard R. Link" <firstname.lastname@example.org> writes:
> > My experience is rather that people usually stick to their core packages
> > as personal property and won't except patches to make them more well
> > behaved.
> That experience aside, we're not talking about patches here, assuming
> Marco's description of the situation is correct. We're talking about a
> full-blown fork and a need for a new udev upstream. You don't need to
> send patches to anyone for that; you need to set up a Git repository, a
> web page, a development mailing list, some infrastructure around how
> you're going to maintain the software, and start doing regular releases,
> and then see about getting Debian to switch upstreams.
> > If people maintain some core piece of software and want to decide what
> > the package looks like, listen to what other people want.
> This isn't about the package. It's about the *software*, the part that we
> generally use from upstream as much as possible because asking people to
> be both upstream and the Debian package maintainer is generally too much
> work for one person or even a small packaging team.
If the maintainer refuses patches and only wants to fix brokeness if
someone does a full blown upstream fork then this is a maintainer issue.
Bernhard R. Link