Re: RFS: phing (Another try)
I splitted the package and created a phing-doc package that hold the documentation.
2011/7/2 Arno Töll <firstname.lastname@example.org>
-----BEGIN PGP SIGNED MESSAGE-----Hi,
On 02.07.2011 17:54, Nicolas wrote:
>> Another thing though; I just noticed that out of the 18MB of the
>> unpacked .deb, 15MB are documentation. I would say it's definitely worth
>> having a separate phing-doc package in this case.
> Good idea.
I didn't have a deep look into your package. However now, Benoît
mentioned the huge docs for your package, you also have to notice that
Debian requires the 'main' repository to be self-containing. This is
what the Debian social contract mandates.
Having a brief look in your upstream's doc/ directory I noticed, you
ship both, generated API docs and a PDF file, perhaps even more stuff
like that. You have to make sure both resources can be regenerated (or
changed, regarding the PDF file) during packaging with build
dependencies available in Debian. This means for you, you should provide
a target in your rules file, which regenerates this documentation the
way, they are created upstream.
While it is not required to rebuild them anytime (or at least, this is
what most people seem to agree) you must provide the possibility to do
so if desired. Otherwise you would have to cleanup your package from
non-free stuff or move it contrib/non-free depending on licenses and
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-----
Archive: 4E0F4523.email@example.com" target="_blank">http://lists.debian.org/4E0F4523.firstname.lastname@example.org