[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

git-buildpackage, dfsg-clean branches, tarballs and non-distributable files



Hi all,

In the spotweb package[0], currently in the NEW queue, I have a git
upstream branch, a dfsg branch and a debian branch. The upstream branch
is pulled from the upstream git repository, then merged into the dfsg
branch, with a number of files removed. The dfsg branch is then merged
into the debian branch, from which git-buildpackage builds the Debian
package.

My questions are:
- the debian/rules get-orig-source target is supposed to build the dfsg
tarball from the canonical upstream source location. That is, NOT from
my own dfsg branch. Which is a bit weird. How do other people handle
that situation? git-buildpackage could create the dfsg tarball from a
tag in the dfsg branch, but this is not exactly the same as the thing
the get-orig-source target does.
- the upstream branch contains a non-distributable font file. If I push
only the debian and dfsg branches to my VCS repository [1], they also
bring with them the entire upstream branch including the
non-distributable file. How can I correctly publish the Debian packaging
in the VCS without also publishing the non-distributable files?

Thank you for any comments,

Jan-Pascal

[0] http://mentors.debian.net/package/spotweb
[1] http://anonscm.debian.org/gitweb/?p=users/janpascal-guest/spotweb.git

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: