[Freeassociation-devel] dpkg-buildpackage

crass at berlios.de crass at berlios.de
Sat Feb 27 18:25:05 PST 2010


On Sat, 27 Feb 2010 12:15:34 -0500
"Wilfried Goesgens" <room_freeassociation-devel at uncensored.citadel.org>
wrote:

>    
> >  Sa Feb 27 2010 08:01:52 EST von  "Fathi Boudra"
> > <fboudra at gmail.com> 
> >Betreff: Re: [Freeassociation-devel] dpkg-buildpackage
> >
> >  On Sat, Feb 27, 2010 at 12:37 PM, Wilfried Goesgens
> > <room_freeassociation-devel at uncensored.citadel.org> wrote:
> >  
> >>crass, fati,
> >> 
> >> why does it take several iterations of configure now?
> >> 
> >>
> 
> >  crass has added python build but i guess we could improve it.
> > have you seen my question about which Debian version should support
> > our debian directory ? >= 4.0 or >= 5.0 ?
> > 
> > When you asked for an optional python build, are you thinking about
> > using DEB_BUILD_OPTIONS ?
> > 
> > Cheers,
> > 
> > Fathi
> > 
> >
> >
> >  
> 
>   
> 
> hm, I still compile these pacakages for debian.citadel.org
> (though .44 didn't work which you probably know 'caus you've fixed
> it...) so i'd like to keep the version for a while so I don't need
> backporting  
> 
> in general, yes, i'd like to en/disable the python bindings like
> 'debug' does a debug build...  
> 
> I'd say my roundtrip doubles with the python bindings.  
> 
>    
> 
> Wilfried Goesgens

Wilfried, I'm new to deb packaging so I didn't know how to do this.  I
tried to make the debian/rules file such that it was easy to not build
the python stuff (*-c rules for C lib, and *-python* rules for python).
Perhaps Fathi can help with this.

The deb build now does X + 1 configures, where X is the number of
python versions you have installed (for me its 2, 2.5 and 2.6) and the
1 is for the libical C library.  I originally had only X configures,
but it was building the C library everytime (which is a lot longer).
Using the current build system there must be at least one configure per
python version because the configure creates makefiles based on that
version.  If we were using distutils I think this issue would go away,
but I'm not that familiar with distutils either.

I would like to know how to turn off the building/creating of a package
which is defined in the control file.






More information about the libical-devel mailing list