Hi, On Fri, Apr 25, 2014 at 06:56:33PM +0000, Patrick Schleizer wrote: > >> I am upstream as well as would like to become a debian maintainer some > >> day. Still learning packaging.
So what you need is a simple solution. > >> Due to the luxury of being upstream as well, the upstream source package > >> can be formatted in any way I wish. [In this case it is a simple package > >> with shell scripts only.] The first thing to do is read the GNU coding standard. Especially around "7.2.4 DESTDIR: Support for Staged Installs". http://www.gnu.org/prep/standards/standards.html#DESTDIR If your Makefile follows this part of GNU coding standard and install files into the right PATH with DESTDIR support, you do not need create the package.install file. This certainly takes more typing than creating package.install but it is very educational. If you do, your debian/rules can be as simple as: ---- %: dh $@ ---- See followings as the starting guide. Debian New Maintainers' Guide: https://www.debian.org/doc/devel-manuals.en.html#maint-guide Introduction to Debian packaging https://www.debian.org/doc/devel-manuals.en.html#packaging-tutorial > Russ Allbery: > > For all of the Stanford-internal packages that we make that are just > > collections of scripts like that, we use the following rune in > > debian/rules: > > > > override_dh_auto_install: > > rsync -C --recursive --links --perms --times --delete \ > > --exclude debian --exclude t --exclude .gitignore \ > > $(CURDIR)/ debian/$(PACKAGE) Very elegant hack :-) indeed for people who know every details. I should remember this. But this may be too much for a novice starting to write upstream package and packaging it. Regards, Osamu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140426133219.GA29369@goofy
