Re: RFS: git2cl
-----BEGIN PGP SIGNED MESSAGE-----
On 03.12.2011 09:23, Dmitry Smirnov wrote:
> However I'm not too sure if introdicing another build-dependency worth
> regenerating single file merely to get almost the same file (but generated) as
> result. Not to mention the effort to implement rather trivial but nevertheless
> the change.
Paul asked me to elaborate why you shouldn't be doing that, as I
coincidentally discussed the same argument in IRC earlier today. Note,
this is not primarily a technical decision, but a legal one.
We require all software in main to be self-contained. That means every
binary package must be able to be reproduced by DFSG free tools in order
to be kept in main. In your case that would mean, to be actually sure
your package fulfills that requirement, you should be rebuilding the
HTML docs by using asciidoc. That might sound trivial, and in your case
it most likely is, but in some cases that's not an easy task at all.
To keep that certainty over time it is a good idea to be rebuilding
every single bit in your package from source every time a new upload has
been made. You shouldn't worry about the build dependencies, the buildds
won't care (much). Hence, not building something from source in favor of
stuff somehow being pre-processed for a DFSG free package is a poor
Finally please note, asciidoc could be cleaned of its recommends as they
aren't really qualifying for "recommends" which would make the
dependencies itself substantially smaller.
with kind regards,
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----