Re: the right way to handle caps in package/program names

MoiN 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 binary. When I left things as they were upstream, dh_make doesn't complain,

the right way to handle caps in package/program names

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" binary. 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.

the right way to handle caps in package/program names

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 binary. 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.

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 binary. Is there a prescribed method for handling upstream source like this?