On Fri, 23 Mar 2007 13:42:30 +0000 Colin Turner <ct@piglets.com> wrote: > I'm busy packaging my own software (OPUS, ITP Bug#415241) for > submission, and I'm most of the way there. I have two questions > though: > > 1. Original tarballs > > There obviously isn't an original tarball that I have patched for > Debian, since I am the upstream author too. It seems clear that Debian > still wants an original tarball created. Should I strip the "debian" > directory from my source code when creating the tarball? Yes. If this package has any prospect of being useful outside Debian, create an upstream location (SourceForge etc.) and REMOVE debian/ from the distributed tarball. It is fine to keep debian/ in CVS/SVN/whatever - you can always use that for your own packaging. If you are creating a package that is Debian-specific (something based on dpkg or apt or only functional with .deb files etc.), then you can consider a native package, hosted at e.g. alioth and then you do keep the debian/ with the package. > 2. Using debconf to notify in postinst > > Part of the install is to create a database with given credentials and > import a schema. I have debconf prompting for values and I'm > successfully using these in the postinst script. There are handlers for this kind of operation - take a look at the source code for serendipity as an off-the-cuff example. > Any help is welcome, the full source is visible here: > > http://foss.ulster.ac.uk/cgi-bin/viewcvs.cgi/?root=opus > > if anyone wants to see more of the debian directory. You should provide the location to the build .dsc file normally, Debian is not usually concerned with creating a package from your CVS, the package is built from a tarball that you build/export from your CVS. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpcHvr1TtLUw.pgp
Description: PGP signature