[Freeassociation-devel] Python bindings overhaul

[crass at berlios.de]

Thanks.  I assume that non-python related patches should go through you
guys (let me know if I should use my best judgment on committing fixes
to other code).  If this is the case, has anyone reviewed my
"icalproperty_kind_and_string_to_enum" patch?

In terms of the debian build, I'm fairly new.  Any pointers on how to
make the building of a debian package optional?  Or do you mean that
you don't want the libical0 package to contain the python module?  I'm
currently setting the deb build to build a separate python-libical
package.  So it will only use more resources when building the debs,
but you can of course choose not to install it.

On Thu, 25 Feb 2010 14:31:52 -0500
"dothebart" <room_freeassociation-devel at uncensored.citadel.org> wrote:

> Ok, added.  
> 
> please make it optional in the debian/rules, since I also use this on
> my netbook where I don't want to clog up my tiny disk with additional
> stuff.  
> 
> The packages in debian.org and ubuntu are maintained by Fabo in
> different places anyway; he will probably add your flags when its
> ready for primetime. 
> >
> >  Do Feb 25 2010 11:13:32 EST von  "crass" <crass at berlios.de>
> > Betreff: Re:
> >[Freeassociation-devel] Python bindings overhaul
> >
> >  I'm not sure how to join the sourceforge project (I think you must
> > add me).  My sf username is gwashburn.  I'm also working on
> > updating the debian files to include the building of a python deb
> > package.
> > 
> > Thanks
> > 
> > On Thu, 25 Feb 2010 07:28:28 -0500
> > "Wilfried Goesgens"
> > <room_freeassociation-devel at uncensored.citadel.org> wrote:
> > 
> >  
> >>Crass, 
> >> 
> >> If you want to take the maintainership of the python code, please
> >> join the sourceforge project, and I'll give you commit access. 
> >> 
> >> I've got more to do with my time than being an svn proxy ;-) and
> >> can't judge the correctness of python code anyway. 
> >> 
> >>  
> >> 
> >> Persistant apis across bindings are probably a good idea. 
> >> 
> >>  
> >> 
> >> For the C++ code, its currently unmaintained too, I also don't know
> >> any opensource project currently making use of it. 
> >> 
> >> but, since some of the package maintainers ship it (afaik) breaking
> >> compile there would be a bigger set back. 
> >> 
> >> Since Art is preparing for a release, I'd wait messing with that
> >> after that release. 
> >> 
> >>  
> >> 
> >> Wilfried Goesgens
> >>
> 
> >  
> >
> >
> >  
> 
>   
> 
>