[Cairo] Re: Xrender transforms...

Sven Luther sven.luther at wanadoo.fr
Thu Aug 14 10:05:45 PDT 2003

On Thu, Aug 14, 2003 at 09:34:25AM -0700, Keith Packard wrote:
> Around 8 o'clock on Aug 14, Sven Luther wrote:
> > But still, what i ask is not joining all the libraries, just to have
> > them in a common source package, and having them buildable in one go,
> > not the build-install repetition we have today, and which will probably
> > not survive well a delayed install like what is done when building
> > packages.
> That's really a packaging and release management issue -- creating

Yes it is.

> a build system to take the various packages and get them built for 
> installation or distribution can be managed by something like 'gar'.

Why not standard build systems ? Just being able to do a :

  tar xzvf tarball.tar.gz
  cd dir
  <some auto stuff>
  make install DESTDIR=/path/to/where/i/want/it

Is a good goal. The only difference with what we have now is that you do
this multiple times for each package, and each package has to be
installed before the other build system can find it. I think one can do
this almost with playing with LD_PRELOAD or something such, and the
autotools can probably also handle them, but it is more complicated.

What about (i don't speak about CVS, but once there are released
tarballs which get made) that having all the different libraries in the
same tarball, but in a subdirectory, and moving the auto/config stuff in
the top directory or something, and then having the possibility to build
the none mandatory libs (ic and xregion) or not, would be much more
sane. Especially given the small size of those libraries.

> I'm not quite sure what to do with 'slim'; I'd like to share the 
> definitions among the libraries which use that technique, but shipping two 
> headers as a package seems a bit extreme.

Even for the ic and xregion libs, it is extreme. It could be ok to make
them binary packages, but they should go in the same source package (and
thus the same source tarball).

> How does 'gnome' get built for debian?

There is one gnome-libs source package, which generate the various
library packages (lignome32, libgnomeui32, ...). I don't know if the
tarballs are pristine upstream ones, or if they are doctored to be made
one tarball.


Sven Luther

More information about the cairo mailing list