Re: the "right" way to handle caps in package/program names
On Sat, Dec 02, 2000 at 08:28:49AM -0700, tony mancill wrote:
> I'm working on a package for ripperX, which comes in a ripperX_2.0 tarball
> and extracts itself into ripperX-2.0 directory, and produces a "ripperX"
> When I left things as they were upstream, dh_make doesn't complain, but I
> get all kinds of problems actually trying to build the package. (dpkg
> doesn't like the control file with caps in the package name, and when I
> fix that, then the orig.tar doesn't match, etc.)
I think this should be handeled by dpkg-source. Just make sure
your build directory is named e.g. ripperx-2.0 and the original
tar archive is named ripperx_2.0.orig.tar.gz. dpkg-source will
take care of renaming directories in the orig.tar.gz file so you
don't need to change that. Often it is not neccassary to change
the contents of the upstream tarfile, but almost always the
_name_ of the tarfile has to be changed.
> Is there a prescribed method for handling upstream source like this?
> Should I fold the directory name in the tarball into lowercase? Since the
> package name is going to be lowercase, it seems confusing that the binary
> is mixed-case. Should I provide a symlink? Fold the binary name itself
> into lowercase? (The same applies for the manpage too, I guess.)
The most prominent example providing an uppercase binary probably
is X. I would not change the name of the binary to keep the
debian package compatible with other installations. However you
shold mention the actual name of the binary in the package
description. I don't know if a symlink is a good idea, I'd ask
the upstream author about that.
<mrvn> Unter Linux gibts es nur zwei Gruende neu zu booten:
1. Man kriegt neue Hardware,
2. Man muss beim Booten ein Huhn ueber der Tastatur opfern.
-- #debian.de, IRCNet