[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Best practices for kernel patches?



On Fri, Dec 07, 2001 at 07:23:00AM +1100, Herbert Xu wrote:
> On Thu, Dec 06, 2001 at 07:30:10AM -0500, Matt Zimmerman wrote:
> > I have started work on packaging a kernel patch, and I've run into an issue
> > that I'm sure that others have dealt with already.

> > Should kernel-patch packages contain diffs against the official kernel, or
> > against the patched Debian sources?

> IMHO the best option is to not package them at all.  Kernel-patch packages
> were originally devised to allow us to maintain kernel packages for
> multiple architectures as the upstream kernel doesn't work out of the
> box on all of them.

> It still doesn't, yet we're now using kernel-patch packages for every single
> patch out there.  This is not what it was designed for and that is why
> you're finding all these problems.

As a user and a package-junkie, I have to say that I've been quite
pleased with all of the kernel patch packages that I've worked with.
And who wouldn't be, when compiling a kernel with IPSEC, PPTP, and AFS
support is as simple as downloading four packages and running a single
command?

Naturally, it's not the end of the world if some patches are not
available as packages; but as long as there are maintainers willing to
put effort into making such packages work, I'd like them to know that
there are users who appreciate the trouble they've gone to.

Steve Langasek
postmodern programmer

Attachment: pgpSa8H6KSnSv.pgp
Description: PGP signature


Reply to: