public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Daniel Drake <dsd@gentoo.org>, Ben Collins <bcollins@ubuntu.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Ubuntu kernel tree
Date: Mon, 7 Nov 2005 18:32:01 +0100	[thread overview]
Message-ID: <20051107173201.GF3847@stusta.de> (raw)
In-Reply-To: <1131383144.2477.9.camel@capoeira>

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


  parent reply	other threads:[~2005-11-07 17:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-06  1:37 [ANNOUNCE] Ubuntu kernel tree Ben Collins
2005-11-06 10:54 ` Jon Masters
2005-11-06 11:03 ` Rogério Brito
2005-11-06 14:48 ` Daniel Drake
2005-11-06 19:02   ` Jon Masters
2005-11-06 22:38   ` Alan Cox
2005-11-07 16:33     ` Daniel Drake
2005-11-07 17:08       ` Alan Cox
2005-11-07 17:05         ` Xavier Bestel
2005-11-07 17:23           ` Michael Alan Dorman
2005-11-07 17:32           ` Adrian Bunk [this message]
2005-11-09 14:09             ` Ben Collins
2005-11-06 20:26 ` Pavel Machek
2005-11-09 14:12   ` Ben Collins
2005-11-09 22:20     ` Greg KH
2005-11-06 20:36 ` Greg KH
2005-11-09 14:13   ` Ben Collins
  -- strict thread matches above, loose matches on Subject: below --
2005-11-07 16:44 Xose Vazquez Perez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051107173201.GF3847@stusta.de \
    --to=bunk@stusta.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcollins@ubuntu.com \
    --cc=dsd@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox