<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Thanks for the quick response! Comments inline.<br>
<br>
sim wrote:
<blockquote cite="mid20060529140328.GA23710@puddle.ca" type="cite">
<pre wrap="">On Mon, May 29, 2006 at 01:26:36PM +0100, Sam Liddicott wrote:
</pre>
<br>
<blockquote type="cite">
<pre wrap="">2. bug in debian dependancies;
instead of depending on
python<2.4
it should depend on
python<2.4 || python2.3 || python2.2
</pre>
</blockquote>
<pre wrap=""><!---->
The actual line in the control file is this:
Depends: ${python:Depends}, python-pyvorbis, python-id3, mpg321, vorbis-tools
mp3togo uses the new CDBS, or the Common Debian Build System. CDBS
automates most of the packaging chores, the rules file is reduced to six
lines, and helps to ensure policy compliance.
Quoting the Debian Python policy manual:
"""1.3.1 Interpreter Name
Python scripts depending on the default Python version (see Main
package, Section 1.2) or not depending on a specific Python version
should use python (unversioned) as the interpreter name.
Python scripts that only work with a specific Python version must
explicitely use the versioned interpreter name (pythonX.Y). """
"""2.4 Dependencies
Packaged modules available for the default Python version as described
in Support Only The Default Version, Section 2.2.1 must depend on
"python (>= X.Y), python (<< X.Y+1)". If they require other modules to
work, they must depend on the corresponding python-foo. They must not
depend on any pythonX.Y-foo.
Packaged modules available for one particular version of Python must
depend on the corresponding pythonX.Y package instead. If they need
other modules, they must depend on the corresponding pythonX.Y-foo
packages, and must not depend on any python-foo."""
CDBS automaticaly generates the control file depends line as follows:
Depends: python (>= 2.3), python (<< 2.4), python-pyvorbis, python-id3, mpg321, vorbis-tools
</pre>
</blockquote>
Indeed, I noticed looking in the debian folder of the source (after I
posted here) that you weren't so explicit.<br>
<blockquote cite="mid20060529140328.GA23710@puddle.ca" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">This fits common ways of installing multiple python ans my ubuntu
installation.
</pre>
</blockquote>
<pre wrap=""><!---->
The Debian package on the website is exactly that; a Debian package.
Judging from my server logs, it has been downloaded more times by Ubuntu
users, however the package is targeted for Debian.
I've been a long time Debian user. This is my first Debian package, I am
by no means an expert. My goal is to get the package into the main
distribution and that requires policy compliance.
I'm not an Ubuntu user and know very little about the OS. I'm happy that
Ubuntu users have found my program to be useful. If I can make changes
to the package that are Debian neutral and help Ubuntu, I gladly will.
I'd also be happy to host an Ubuntu specific package, but creating one
is beyond the scope of my skills.
</pre>
</blockquote>
My history goes redhat->debian->ubuntu, but whereas I could learn
to produce RPM .spec files after a couple of hours, but even now debian
packages still leave me baffled how they can keep something so hard for
so long :-)<br>
<blockquote cite="mid20060529140328.GA23710@puddle.ca" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">Also the interpreter line (line 1) we need a cunning way to specify the
right python, perhaps the install scriptlet should fix this up? Or some
generic python head which feeds the main body to the right python?
</pre>
</blockquote>
<pre wrap=""><!---->
mp3togo makes use of generators, so requires at least the default
Debian version 2.3, aside from that, there is nothing particularly
version specific. It is reported to run on 2.4 with no problems.
</pre>
</blockquote>
indeed, in fact I made things work by skipping the debian package and
just installing the usual way, and then it worked with python2.4;
otherwise mp3togo kept failing when applying tags to the recoded mp3's<br>
<br>
<blockquote cite="mid20060529140328.GA23710@puddle.ca" type="cite">
<pre wrap="">Thanks for your interest Sam, I hope my Debian-centrism is not too
inconvenient for you.
</pre>
</blockquote>
building debs may be, but you're not. I still use debian for all my
servers.<br>
<br>
Anyway, mp3togo is what I needed for years; thanks!<br>
<br>
Sam<br>
<br>
</body>
</html>