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

Re: kernel-patch-debian-2.6.8 and pristine linux 2.6.8 kernel

On Fri, Aug 20, 2004 at 02:43:46AM +0300, Shaul Karl wrote:
> On Wed, Aug 18, 2004 at 12:16:04AM +0200, Christoph Hellwig wrote:
> > On Wed, Aug 18, 2004 at 01:13:08AM +0300, Shaul Karl wrote:
> > > On Tue, Aug 17, 2004 at 04:02:32PM +0200, Christoph Hellwig wrote:
> > > > On Tue, Aug 17, 2004 at 02:17:11PM +0300, Shaul Karl wrote:
> > > > >   The description of kernel-patch-debian-2.6.8 claims that they should
> > > > > be applied to a pristine linux 2.6.8 kernel. Yet I get:
> > > > 
> > > > That statement is wrong.  We'll have to fix it.
> > > > 
> > > 
> > > 
> > >   Why kernel-patch-debian can not have that quality (of applied to
> > > pristine linux kernel)? Doesn't it a service to the users and helps them
> > > to avoid running diff by themselves? Being able to tell where one's 
> > > kernel differs from someone else kernel helps when discussing and
> > > learning the kernel.
> > 
> > Talk to the firmware-removal zealots.
> > 
>   Do you mean that distributing the diffs with lines like
> -# a line that it was decided not to distribute
> -# another line that shouldn't be distributed
> -# yet another one
> is similar to distributing lines that it was decided not to distribute?

Indeed. Be it only because you can take the resulting kernel-source and
reverse apply the patch.

> If so, can't the debian-patch package have a shell script that rm the 
> entire files with the these sort of problems and then have the diff only
> contain the lines that were approved?

Heu, i believe this may be to fragile for automated intervention.

>   I hope that this arrangements is acceptable by everyone while still 
> helping at least users who are mostly interested in the code that Debian
> does distributes. Hopefully these are most of the users.

What is the real problem ? you don't want to use the debian kernel, but the
upstream one, it is up to you. you get the individual debian patches, and
apply all of them to your kernel-source, except the ones that touch the
firmwared stuff or whatever.

Christoph, i don't remember if the debian-patch package does include also the
standalone patches, or only the global debian version ones. Maybe the easiest
thing would be some tag in the DP: lines of the dpatches that mark a patch as
touching not-upstream-clean stuff, and have a script or something to apply,
with an option to include or not those.


Sven Luther

Reply to: