Bug#269961: Reintroduce doc++ to sarge, Build-Depends for other packages

[Stefan Gybas]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDF6C783C7547B4D35BBF3A2F
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Mark Purcell wrote:

> It would appear that doc++ was incorrectly removed from both testing and 
> unstable as it was thought that it was obsoleted by a Java documentation 
> package, however doc++ was also an important Build-Depends for a number of 
> packages in sarge (See #265273 for history):

Sorry, this was my fault! I thought that only Java packages were using 
doc++ as a replacement for javadoc. The pkg-java team switched most of 
the Java packages to gjdoc and when I requested the removal of 
mozilla-ldapsdk (the last Java package that was using doc++) I thought 
doc++ could also be removed.

Of course, I should have checked the build dependencies first (I only 
checked package dependencies). Sorry again for the trouble that I've 
caused and for my late reply. I've been away a couple of days since last 
Friday.

If someone wants to take over doc++ you are more than welcome! You 
should probably re-open the closed doc++ bugs and fix them if possible. 
But upstream delevopment seems to have stopped (the last update was in 
December 2002) so doxygen might be a better solution for the packages 
that currently use doc++.

Stefan

--------------enigDF6C783C7547B4D35BBF3A2F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBPu4BCdoSgNrrJGsRAgUWAKDLP6UPoJ9TaHhUGIJkWKl0bPpVEQCeLKw7
k4vvHX2pZHwBqZXOO6gHiI4=
=8YCY
-----END PGP SIGNATURE-----

--------------enigDF6C783C7547B4D35BBF3A2F--