MMA package, install targets

[Joel Roth]

On Tue, Jan 10, 2012 at 10:18:26PM +0100, Reinhard Tartler wrote:
> On Di, Jan 10, 2012 at 20:10:55 (CET), Joel Roth wrote:
> 
> > On Thu, Jan 05, 2012 at 10:12:10AM +0100, Reinhard Tartler wrote:
> >> On Do, Jan 05, 2012 at 08:42:25 (CET), Joel Roth wrote:
> >> 
> >> > Hi Multimedia Maintainers,
> >> >
> >> > I've merged the new upstream version 12.01, 
> >> > now trying to get the package to build.
> >> >
> >> > Could someone check the install targets in
> >> > the files below, or point me to some 
> >> > examples/references? 
> >> >
> >> > Isn't clear which of the following I should be using:
> >> >
> >> > 	debian/mma/usr/bin/executable
> >> > 	/usr/bin/executable
> >> > 	usr/bin/executable
> >> >
> >> 
> >> I see that mma is a python project. I think you can save yourself and
> >> upstream a *lot* of time and headaches if you would write a proper
> >> setup.py using the standard distutils python package.
> >
> > Hi Reinhard,
> >
> > I've put in some time studying distutils and other modules
> > for this purpose. Writing setup.py seems like the right
> > direction for upstream.
> 
> Why not write one right now, use the benefits it brings for the package,
> and then ask upstream to integrate your package?

I'll need to go through the app and replace all paths with
references to sys.prefix. But yes, the app is well
organized, and it would be possible to do with quilt,
if not upstream.  It's slow for me, being new to the
language and its conventions.

> > For the moment, I have corrected the installation paths in
> > d/mma.install and d/rules. 
> 
> What you did looks, at least on the first look, correct, but does not
> help upstream or other distributors.

The app already has install scripts that work on 
OS X, Windows and Linux, and have been working
fine for eight years. 
 
> > Is commiting dch -r sufficient to signal uploaders
> > to review the package?
> 
> At least I scan PET when I have some spare time:
> http://pet.debian.net/pkg-multimedia/pet.cgi
> 
> I notice that the mma package list only you as Uploader. Who else from
> the team is going to back you up in case you become unavailable or
> otherwise too busy to care for the package?

I agree that this another argument to use setup.py
I'm all for using standard methods and tools. 

OTOH, 
1. the app is mature, and isn't expected to change much.
2. I'm working with upstream to convert to distutils,
   and at that point we can easily import a new upstream version 
   with these improvements.
3. I would like to release something usable when that 
   is possible; having done enough to get the package
   to install, why *not* release?

 
> Also, the package has been removed from unstable for being buggy and
> dead upstream. What has changed since September 2010? This needs to be
> documented and discussed in a new ITP bug, which is then closed in
> debian/changelog (at least IMO).

AFAIK, the package never made it to unstable. Since Sept
2010 a new upstream version was released. I imported it
into the Debian multimedia git repository.

Do I need to open an new ITP bug?

Thanks for your attention!

Joel
 
> Cheers,
> Reinhard
> 
> -- 
> Gruesse/greetings,
> Reinhard Tartler, KeyID 945348A4
-- 
Joel Roth