Re: first package pcftisio
On Tue, Feb 21, 2006 at 02:22:05PM +0100, Cedric BRINER wrote:
> > You should try to get some better response than this. Creative works
> > are, by default, copyrighted. At the very least you need to get the
> > author to send you an email (or make another release of the software)
> > stating that it is released into the "public domain", which is as
> > close to "no copyright" as you can get. The alternative is for him to
> > assert a copyright on the software (simply by putting "Copyright (C)
> > 200X-2006 Nor ...." in the source files), and including some license
> > statement to allow its distribution etc. Commonly suggested licenses
> > are the X11/MIT license (a 'liberal' one), and the GPLv2 (a 'copyleft'
> > one).
> I'm waiting for his response.
Great, thanks :)
> And I still have some questions
>
> - Do you know in which sections shall I put this package which is related
> to python, astronomy ? (how should I proceed to know in which section to put it)
Either python or science; a list of possibilities is at:
http://www.us.debian.org/doc/debian-policy/ch-archive.html#s-subsections
> - After trying to make the debian source with the help of the book:"the
> Debian System". I'm getting some errors after doing:
> dpkg-source -b python-cfitsio-0.99.2/
> dpkg-source: building python-cfitsio using existing python-cfitsio_0.99.2.orig.tar.gz
> dpkg-source: building python-cfitsio in python-cfitsio_0.99.2-1.diff.gz
> dpkg-source: cannot represent change to debian/python-cfitsio/usr/lib/python2.3/site-packages/pcfitsio.so: binary file contents changed
./debian/python-cfitsio should be cleaned in the clean target by
dh_clean; I don't know why this isn't happening.
> dpkg-source: cannot represent change to build/lib.linux-i686-2.3/pcfitsio.so: binary file contents changed
> dpkg-source: cannot represent change to build/temp.linux-i686-2.3/pcfitsio.o: binary file contents changed
> dpkg-source: cannot represent change to build/temp.linux-i686-2.3/pcfitsio_wrap.o: binary file contents changed
You'll need to remove this also in the clean target; if the upstream
makefile doesn't do it, you might remove them manually ($(RM)) or if
that directory is recreated (or if you recreate it) just rm -fr
./build/.
> # edit the debian rules, control, copyright
> cat control
> Source: python-cfitsio
> Section: unknown
> Priority: optional
> Maintainer: BRINER Cedric <cedric.briner@obs.unige.ch>
First name first, and each name in lowercase except for the first
letter only, please.
> --- rules 2006-02-21 13:56:45.000000000 +0100
> +++ ../../../0.99.2/python-cfitsio-0.99.2/debian/rules 2006-02-21 13:44:52.000000000 +0100
> @@ -24,6 +24,11 @@
> configure-stamp:
> dh_testdir
> # Add here commands to configure the package.
> + sed setup.cfg \
> + -e 's|include_dirs=.*|include_dirs=/usr/include|g' \
> + -e 's|library_dirs=.*|library_dirs=/usr/lib|g' \
> + -e 's|inplace=.*|inplace=0|g' > setup.2.cfg
> + mv setup.2.cfg setup.cfg
>
> touch configure-stamp
You don't really need configure stamp at all; sed will run in about
0.01 seconds :)
For that matter, you don't really even need a separate configure
target; you could just put this all into "build".
Also, if you don't need this package to build on sarge, you can use
sed -i.
(Btw, don't use sed -n -i without caution..)
> @@ -34,7 +39,7 @@
> dh_testdir
>
> # Add here commands to compile the package.
> - $(MAKE)
> + #$(MAKE)
> #docbook-to-man debian/python-cfitsio.sgml > python-cfitsio.1
>
> touch build-stamp
If the build target doesn't do anything, you don't need anything
there, and you certainly don't need the build-stamp; but I don't see
that you call the setup.py here:
> # build
> python setup.py build
You don't need to keep the commented out rules parts.
> -# dh_python
> + dh_python
If you use this program, your package should build-depend on python.
Have you read the python policy?
http://www.us.debian.org/doc/packaging-manuals/python-policy/
Justin
Reply to: