On Sunday 30 November 2014 20:32:26 T o n g wrote: > On Sun, 30 Nov 2014 18:12:06 +0100, Santiago Vila wrote: > >> > In the past, having a `debian/` directory upstream was a pain because > >> > we didn't have a proper way to remove a file if needed. Nowadays, it > >> > is perfectly fine if you use a 3.0 format. > >> > >> Fine in which way ? > > > > It's fine because, for a 3.0 quilt package, "dpkg-source -x" unpacks the > > .orig.tar.gz, removes all the debian/* files coming from upstream > > tarball, if any, and then unpacks the *.debian.tar.xz file. > > Ok, good to know, but that's more targeting towards package building, not > source code developing and maintaining. Does it imply that I should put > the `debian` folder within my source tree now? Because as mentioned > before, the last thing I want to do is to separate my source and my > `debian` folder into two git repos. Why not create an empty branch 'debian' and move your debian related stuff there. Whenever you e.g. make a release, just merge your release branch into the debian one, create packages. Amend your .gitignore so that everything works smoothly. That is what my sponsor suggested (for https://github.com/rockdaboot/libpsl/). Tim
Attachment:
signature.asc
Description: This is a digitally signed message part.