Package: dgit Version: 0.12 Severity: wishlist Joey Hess writes ("dgit feedback"): > * It turns out to not be uncommon for a package's git repository to not > contain files that are included in the package's tarball. At least for > native packages. Some examples include generated man pages that the > clean taget forgot to remove and that the .gitignore hid from notice, > .pot files that were not checked into git due to being autogenerated, > but were included in the tarball, and .po files that often change in > uninteresting ways during the build (line numbers and dates) that were > blocked from being committed to git. > > The second problem is common enough that a lot of people will encounter > it when using dgit. If they are only using the dgit repository it might > be easy enough to git add the files and move on. > > OTOH, when using dgit with another git repository, it might require > revisiting past decisions about what should be checked into the git > repository, which may involve others in the team and could be > contentious. > > Seems that the end result is more consistent and clean, but I think this > is a potential adoption blocker to keep an eye on..
I replied by email, but I think this ought to be discussed in the manpage. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org