On Mon, Nov 07, 2005 at 06:05:44PM +0100, Xavier Bestel wrote:
> On Mon, 2005-11-07 at 18:08, Alan Cox wrote:
> > On Llu, 2005-11-07 at 16:33 +0000, Daniel Drake wrote:
> > > Source RPM's will just contain a Linux kernel tree with your patches already
> > > applied, right?
> >
> > Of course not. Its an rpm file. RPM files contain a set of broken out
> > patches and base tar ball plus controlling rules for application. It's
> > rather more advanced than .deb sources.
>
> That's a troll, Alan. .deb contain exactely the same things.
No, he's right.
The changes a package maintainer does in a .deb are shipped in one big
diff containing all the differences between the pristine upstream
sources and the tree used for building the package.
There are now ways how to arrange the patches in a way that they are
visible as separate patches inside the unpackaged source tree used for
building the package [1], but if all you are interested in is to get the
patches applied against the upstream sources RPM is still superior
(even on my Debian system mc can extract the patches as if the RPM was a
tar file).
> Xav
cu
Adrian
[1] that are used by a subset of the packages shipped by Debian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]