[Mono-docs-list] monodoc split

[Peter Williams]

Something along these lines sounds like a good idea to me. 

It leads me to another question though: does monodoc have a maintainer
of sorts? There are a few features and bugs that would be nice to
address, and I hope no one will be offended if I say that the code could
use a little bit of prettifying. I'd like to pitch in but there doesn't
really seem to be a go-to person for patches, though.

Peter

On Thu, 2004-07-22 at 14:56, John Luke wrote:
> Hello all,
> 
> At the risk of being rejected, I would like to propose that monodoc be
> split into at least two seperate packages. I know this has been
> discussed before, but I don't recall anyone ever formally asking. 
> This is primarily for the following reasons:
> - So Gtk# can depend on monodoc-common to conditionally build and install its
> docs while avoiding the circular dependencies.  This will allow those
> building from cvs or newer Gtk# tarballs to get those docs installed
> automatically, and uncouples the two packages.
> - The doc build has grown to taken a substantially large time, so that
>   building monodoc from a tarball or cvs sucks (at least for me).
> 
> So my request is (name however you want):
> monodoc-common - contains the docs, tools, monodoc.dll, mod, the monodoc pc file
> monodoc - contains the Gtk# frontend (and the web stuff if you want)
> 
> I volunteer to do this if it is a time constraint for you to do so.
> 
> Thanks
> _______________________________________________
> Mono-docs-list maillist  -  Mono-docs-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-docs-list
-- 
Peter Williams                          peter@newton.cx

"[Ninjas] are cool; and by cool, I mean totally sweet."
                              -- REAL Ultimate Power