Re: RFS: projectm (ping)
On Sat, 19 Jun 2010 21:31:37 +0200 Matthias Klumpp wrote:
> Hello!
>
> I'm still looking for someone interested in reviewing & sponsoring my
> packaging of projectM.
>
> Package details:
>
> * Package name : projectm
> Version : 2.0.1-1
> Upstream Author : projectM Team
> * URL : http://projectm.sf.net
> * License : GPLv2 and LGPLv2.1
> Section : sound
>
> It builds these binary packages:
> libprojectm-dev - Advanced Milkdrop-compatible music visualization library
> - dev
> libprojectm-qt-dev - projectM Qt4 (development files)
> libprojectm-qt1 - projectM Qt4 bindings
> libprojectm2 - Advanced Milkdrop-compatible music visualization library
> libvisual-projectm - libvisual module for projectM
> projectm-data - Advanced Milkdrop-compatible music visualization library -
> data
> projectm-jack - projectM JackAudio module
> projectm-pulseaudio - projectM PulseAudio module
>
> The package appears to be lintian clean.
>
> The upload would fix these bugs: 565355
>
> There's some "special" stuff to know about this package: The package
> replaces the orphaned libvisual-projectm package and the libprojectm source
> package.
> I got authorization from the maintainer of libprojectm to take over
> maintainership over this package.
> The pkg produces some Lintian warnings about ancient Autotools scripts or
> Windows binaries in the package. (projectM uses CMake, the
> Autotools-Scripts are just cruft which isn't used) It also has some
> binaries which unnecessarily linked against some libraries. All this
> stuff
> should be
> fixed by upstream, but upstream seems to have a lack of manpower at time,
> so I can't get a clean tarball or fixes for all issues.
You should manually remove any included binaries from the upstream
source, and retar the files as your clean upstream source (otherwise
there is no way to check whether those binaries are dfsg-free). You
can (and should) use the system provided autotools (rather than using
the versions embedded by upstream).
Mike
Reply to: