[Debichem-devel] cclib

Karol M. Langner karol.langner at gmail.com
Thu Apr 14 14:25:29 UTC 2011


On Wed, Apr 13, 2011 at 11:49:37PM +0200, Michael Banck wrote:
> On Wed, Apr 13, 2011 at 08:29:42PM +0200, Daniel Leidert wrote:
> > > W: cclib: package-contains-upstream-install-documentation usr/share/doc/cclib/INSTALL
> > > W: cclib: extra-license-file usr/share/doc/cclib/LICENSE.gz
> > 
> > Both can probably be fixed in debian/patches/fix_setup by removing them
> > from the install targets. Or remove them after the installation step,
> > which doesn't equire patching setup.py. Call
> > 
> > $(RM) debian/cclib/usr/share/doc/cclib/LICENSE ...
> > 
> > in debian/rules. Your choice.
> > 
> > Usually the upstream installation information is useless for the Debian
> > user, because he gets an ready-to-install package. So we check this file
> > for further important information (besides installation information) and
> > put this information into debian/README.Debian and don't install the
> > upstream file.
> > 
> > We also don't ship extra license files. The common license files can be
> > found in /usr/share/common-licenses/ and debian/copyright (installed
> > as /usr/share/doc/{package}/copyright) links to these common files. If
> > the license is not shipped in /usr/share/common-licenses/, then it must
> > be fully reproduced in debian/copyright.
> 
> They referenced in debian/cclib.docs, just removing them from there
> should be enough I guess.

Exactly, that's how I did it.

BTW, here are the packages I get:
http://www.mmqc.org/kml/tmp/cclib/

What's the next step?

- Karol

-- 
written by Karol M. Langner
Thu Apr 14 16:24:47 CEST 2011



More information about the Debichem-devel mailing list