Separation of foo-doc from foo is generally only done when foo-doc is big and/or foo is a required base package (like perl, on Debian).<br><br>Considering perlbal-doc is small and perlbal isn't a required package, I think also that these should be merged.<br>
<br><br><div class="gmail_quote">On Fri, Apr 11, 2008 at 10:18 PM, dormando <<a href="mailto:dormando@rydia.net">dormando@rydia.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It's ... what a lot of packages do :)<br>
<br>
It allows you to help avoid extra manuals across all of your packages if<br>
you want to save space.<br>
<br>
Although, I don't really care much myself, hachi might :)<br>
<font color="#888888"><br>
-Dormando<br>
</font><div><div></div><div class="Wj3C7c"><br>
Andrew McClain wrote:<br>
> Is there a reason why the perlbal debian package is split off into<br>
> perlbal and perlbal-doc?<br>
><br>
> I can't think of a reason why we'd want to cut out the 20K or so of doc<br>
> files, especially when docs aren't the easiest thing to find?<br>
><br>
> I'd like to combine the two packages. Any objections?<br>
><br>
> --<br>
> Tap the collective.<br>
> <a href="http://www.fluther.com" target="_blank">http://www.fluther.com</a><br>
<br>
</div></div></blockquote></div><br>