Module submission - libmusicbrainz

Chad R. Kittel v3rt1g0 at lunar-linux.org
Sat Apr 15 15:30:46 UTC 2006


On Sat, 15 Apr 2006 18:21:15 +0200
"Davide \"M3xican\" Coppola" <dmc at dev-labs.net> wrote:

> bash-3.1# lvu stree libmusicbrainz
> libmusicbrainz: expat
> bash-3.1# lin libmusicbrainz
> Checking dependencies for libmusicbrainz
> Building libmusicbrainz version 2.1.2
...
> 
> The problem is not strictly related to libmusicbrainz, that is 
> successfull compiled,
> but to its python bindings, that use ctypes as you can read in the 
> README into
> the dir python/
> 
> I think that it's stupid have python bindings in the library package, 
> but I'm not the
> author of libmusicbrainz, so the best I can get is make everything
> work fine.

So, what would be appropriate here would be something more like an
optional depends.  Because if libmusicbrainz can compile without Python
support, then adding 'ctypes' in as a required depends, will suck
Python onto your system only to create bindings.  The better way of
doing this is probably to create a python-musicbrainz module to deal
with the bindings themselves and make sure that the libmusicbrainz
module doesn't compile the bindings itself 100% of the time.

A required depends on ctypes seems way over the top just for bindings
to a language you may not even want (need) installed.

> 
> I don't know why u can compile without errors, but I think that now
> this dependence
> is necessary.

I compiled without errors I guess because I don't have Python
installed, but of course we need to support when Python is installed,
hence the dual module approach library separate from bindings would
probably suit everyone best?  What say you?

-- 
  _
(\o/) Chad 'v3rt1g0' Kittel <v3rt1g0 at lunar-linux.org>
 /_\  Milwaukee, WI (USA)  [4 8 15 16 23 42]
"...staring up at heaven from the bottom of a glass" - Savatage


More information about the Lunar mailing list