Dear David, 1. Why do you have a folder full of patches, when you are the upstream author of 4Pane? Have they been applied upstream, but there hasn't been a release of 4Pane recently? DEP-3 has a patch header to indicate that they have been merged upstream, if this is indeed the case. 2. I see that w.r.t. 4pane/4Pane, you're using 4Pane wherever Debian policy permits you too. Good idea. The only thing I'm not sure about is the symlink from /usr/share/doc/4Pane to /usr/share/doc/4pane/html. It could be misleading, since Debian users expect /usr/share/doc/foo to give them a folder containing a changelog, a Debian changelog etc. Why not link to /usr/share/doc/4pane? On Mon, Nov 14, 2016 at 09:30:49PM +0000, David Hart wrote: > For simplicity, I've just removed the tarball. It can always be done properly > in the future when I understand better what is required. Okay. > >Also, the Vcs-* fields still point to the upstream source, not the > >packaging repository. > > Does this need to be fixed before you can use the repo. No. > If so, what should I enter there? Vcs-Git: > https://github.com/dghart/4pane-debian-dir -b master Vcs-browser: > https://github.com/dghart/4pane-debian-dir/tree/master or something > different? You should look up the definitions of the Vcs-* fields in Debian policy :) -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature