I am one of SOAPpy upstream.
Luke Yelavich <[EMAIL PROTECTED]> writes:
Hi all
I am looking into packaging jack_mixer, requested by the upstream
developer on IRC. One of its dependancies is the fpconst module.
As it happens, fpconst can be found in the python-soappy package, which
ahs nothing at all to do with jack_mixer, which is an audio application.
I am wondering where we go from here. Do we separate out fpconst as a
separate package, and have python-soappy depend on that, or should I
place a copy of fpconst in with the new jack_mixer package?
2007/1/30, Reinhard Tartler <[EMAIL PROTECTED]>:
Looking at bugs like
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379113, I'd say it
makes much sense to have a separate python-fpconst package. I wonder if
it makes sense to make the python-soappy package provide the extra
binary package, or if it should go out of python-soappy and create a
new source package.
fpconst is maintained outside of SOAPpy, and is useful in itself.
Therefore, fpconst should be its own source package as well as a
separate binary package.
Correct upstream URL for fpconst would be SourceForge's RSOAP project,
as new release tarballs (well, they are far between) are posted to its
download area.
http://sourceforge.net/projects/rsoap
--
Seo Sanghyeon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
