[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: How to organize guile-gnome
From: |
Andreas Rottmann |
Subject: |
Re: RFC: How to organize guile-gnome |
Date: |
Wed, 03 Dec 2003 19:40:35 +0100 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) |
Greg Troxel <address@hidden> writes:
> My mail was mainly how to organize stuff from a source configuration
> managment POV, not so much how we then partition our modules into
> release tarballs.
>
> I think we are in agreement. From the packager point of view, I want
> to split guile-gnome into pieces to avoid unnecessary dependencies.
>
> > I think it would be really unfortunate if one needed to install
> > gstreamer to build guile-gnome.
> >
> All bit the first (glib/gobject) will be optional in any build (it is
> already).
>
> The possible problem is that it should be possible to build the core
> part and install it, and then build the other parts seperately (as
> opposed to rebuilding the whole thing with more options enabled).
>
Hmm, I don't quite get you; it should be possible to build all parts
that have their *external* dependencies satisfied, so you don't need
to build a part, install that and then go on, so if you have Glib,
libglade, libgda but not GTK+ installed, the bindings for the first
three will build and install, while the GTK+ binding will be left out.
> Eg:
>
> guile-gobject depends on glib2 and guile
> guile-gobject-corba depnds on guile-gobject and ORBit2
> guile-gtk depends on guile-object and gtk
> guile-glade depends on guile-gtk and glade2 (or libglade2)
>
> From this view, having a huge tarball is ok if one can easily take
> parts of it to build/install.
>
I think that this is the case right now.
> This may just be separate install targets for the segments. But
> separate tarballs that each install just their part (and rely on the
> dependent ones being installed already) is the easiest way,
> mentally.
>
Hmm, I think the current model is easy to grasp: configure checks all
*external* dependencies, the bindings for those satisfied are built
(and installed on 'make install').
Andy
--
Andreas Rottmann | address@hidden | address@hidden | address@hidden
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
This reality is really just a fucked-up dream -- Papa Roach
- RFC: How to organize guile-gnome, Andreas Rottmann, 2003/12/03
- Re: RFC: How to organize guile-gnome, Greg Troxel, 2003/12/03
- Re: RFC: How to organize guile-gnome, Andreas Rottmann, 2003/12/03
- Re: RFC: How to organize guile-gnome, Greg Troxel, 2003/12/03
- Re: RFC: How to organize guile-gnome,
Andreas Rottmann <=
- Re: RFC: How to organize guile-gnome, Greg Troxel, 2003/12/03
- Re: RFC: How to organize guile-gnome, Andreas Rottmann, 2003/12/03
- Re: RFC: How to organize guile-gnome, Greg Troxel, 2003/12/03
- Re: RFC: How to organize guile-gnome, Andy Wingo, 2003/12/04
- Re: RFC: How to organize guile-gnome, Greg Troxel, 2003/12/04
- Re: RFC: How to organize guile-gnome, Kevin Ryde, 2003/12/06
Re: RFC: How to organize guile-gnome, Andy Wingo, 2003/12/04