"Mark Purcell" <[EMAIL PROTECTED]> writes: > We provide a patch target, which we felt meets the requirement of policy 2.8. > > debian-devel, is there a view, does one need README.source if you > provide a patch target and use one of the standard patch management > systems? Seems like this would cover 90% of use cases and add very > little value!
The intention was that even those cases would have a README.source file to save people the effort of trying to figure out whether the patch system was really in use and whether there was anything odd about how you were using it. However, there has been some controversy about this and there is an open Policy bug for discussing presenting it a different way. If anyone has opinions on the best way of handling this documentation, please do comment at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495233 I would personally prefer that the documentation file be present with *some* content if any non-standard (read: not supported directly by dpkg) system were in use to avoid having to guess. I don't think just putting the patch system into Build-Depends should be sufficient. But it's possible that I could be outvoted on that. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ pkg-kde-extras mailing list firstname.lastname@example.org http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras