Re: Proposal on how to handle xorg include patches (WAS: Re: X Strike Force XOrg SVN commit: r28 - /)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christoph Hellwig wrote:
| On Tue, Oct 12, 2004 at 09:20:21AM +0200, Fabio Massimo Di Nitto wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>X Strike Force SVN Repository Admin wrote:
|>
|>| +|
|>| +|--> xorg-source-include --> xorg-include
|>
|>Hi XSF,
|>~ as you might have noticed, we started (at low priority) working on
|>X.org packages.
|>
|>The commits you are seeing now are only the proof of concept that we
|>will use to split the tree in a "sort of" modularized way, using an
|>approach close to the way in which our Debian kernel is packaged.
|>There are some differences, but at this point in time, until the concept
|>is not proved to be working, are somehow irrelevant.
|
|
| Note that the -source vs -image package in the kernel are an sbolute
| maintaine horror, I would strongly advice against repeating that
| mistake.
|
|
The main reason why we are using this approach is because X doesn't
evolve as fast as the kernel and it is the only way at the moment to
simulate X.org modularized tree.
In this way each time a package gain its own independency, it will be
dropped silently from the -source- package and a new version of
"independent-source" orig.tar.gz will be uploaded. The good thing is
that all of this can be done without ftp-master manual intervention
(other than the first package approval).
Fabio
- --
<user> fajita: step one
<fajita> Whatever the problem, step one is always to look in the error log.
<user> fajita: step two
<fajita> When in danger or in doubt, step two is to scream and shout.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBbKgxhCzbekR3nhgRAoMIAJ0bsJ7j907oHjWHtbx4v9ACkjVInQCfUB6j
nKjErse8HeY8gLaa1FuQ6A8=
=hnD6
-----END PGP SIGNATURE-----
Reply to: