Merged proto package

Gaetan Nadon memsize at videotron.ca
Wed Apr 7 07:02:54 PDT 2010


On Tue, 2010-04-06 at 18:43 -0700, Keith Packard wrote:

> The goal is to reduce the number of packages required to build the X
> server or drivers from git or from tarballs.
> 

Have you considered using Automake "nested packages" feature?

It may provide the best of both worlds, retaining the desired level of
granularity while distributing a small number of packages.


        "A typical setup is that package A will distribute one of the
        libraries it needs in a subdirectory. This library B is a
        complete package with its own GNU Build System. The configure
        script of A will run the configure script of B as part of its
        execution, building and installing A will also build and install
        B. Generating a distribution for A will also include B."
        
        "It is possible to gather several package like this. GCC is a
        heavy user of this feature. This gives installers a single
        package to configure, build and install, while it allows
        developers to work on subpackages independently."


We can group a number of drivers or protos or whatever (subpackages)
that are under active development in a "driver" (or "protocol") top
package. Other drivers or protos not selected can continue to work the
way they do today. Subpackages can be easily moved in and out. We would
not have to write any script or workaround, just use automake the way it
was designed.

Marketing brochure:
http://www.gnu.org/software/automake/manual/automake.html#Nested-Packages
http://www.gnu.org/software/automake/manual/automake.html#Subpackages

It looks like the details have been well thought out:


        --help=recursive
        
                Print a summary of the options unique to this package's
                configure, and exit. The short variant lists options
                used only in the top level, while the recursive variant
                lists options also present in any nested packages. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20100407/a12772b3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg-devel/attachments/20100407/a12772b3/attachment.pgp>


More information about the xorg-devel mailing list