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

Bug#258043: kernel-patch-debian-2.6.7: doesn't list which patches are incorporated: kernel-patch-debian-2.6.7, kernel-image-2.6.7: doesn't list which patches are incorporated



On Thu, Jul 08, 2004 at 08:58:44AM +0200, Kilian Krause wrote:
> Hi Sven,
> 
> > > /usr/src/kernel-patches/all/2.6.7/debian/patch-2.6.7-1.bz2
> > > /usr/src/kernel-patches/all/2.6.7/debian/patch-2.6.7-2.bz2
> > 
> > For this kind of stuff, it is better to work on the source package of
> > kernel-source. 
> > 
> > try apt-get source kernel-source-2.6.7 and experiment with it.
> 
> my point is: when installing a system and thus adding a new kernel, why
> would i want to install a kernel with patches and settings i don't know?

Because it is the debian kernel, and you trust the debian-kernel
maintainers to know what is best for you.

If this is not the case, then you are big enough to look at the source
package, are you not ? Or even at the kernel-source subversion repo if
the package is too big for you.

Alternatively, the kernel-patch package should provide the patches in
split format, as well as the different patchsets. This is not done yet
though, and would need kernel-package support.

> So all i ask for is a policy-refence for the internal kernel-package
> policy about:
> - which patches are in (more than just the vanilla kernel)
> - which hardware is supported
> - which features are compiled in (like networking etc.)

Sure, but adding this in the package description is overkill, and maybe
even difficult to automate.

> If that can be put on some web page for me to look at, that'd just be
> terrific.

Ah, what is your problem with : 

  http://svn.debian.org/viewcvs/kernel/kernel/2.6/source/trunk/kernel-source-2.6.7-2.6.7/debian/patches

Well, probably the tagged version thereof.

> I *DO* understand that putting that into the description is not what you
> guys want, so ok. Even a pointer to the SVN repository of kernel-source
> would be ok, if that does list what i search for.
> This all shall take place *before* moving some 300 MB (binary images,
> sources, vanilla sources, crawling patch websites etc.) around the net
> until finally finding the kernel-image i really do want to install (and
> reading sources and docs and searching bits and pieces in README and
> TODO files for like 3-4h until i find all info i need to know what went
> into kernel-source).

Like said, if you think you are big enough to know better than the
debian-kernel team, you are also big enough to find out the info you
want all by yourself.

And in any case, just downloading the kernel-patch-debian package should
in the future give you all the info you want.

Friendly,

Sven Luther




Reply to: