[mono-packagers] monodoc & mcs/mono module merging

[Mirco Bauer]

On Fri, 17 Oct 2008 21:10:38 -0400
Jonathan Pryor <jonpryor at vt.edu> wrote:

> > Unanswered Questions:
> 
> What should be done about monodoc/engine/web, the ASP.NET frontend to
> monodoc documentation?  I don't believe that it's actually packaged,
> nor do I know of anyone using it except for http://go-mono.com/docs,

Debian and thus Ubuntu ship the web-frontend of monodoc:
http://packages.debian.org/search?keywords=monodoc-http

And according to popcon 108 installs of it are counted:
http://qa.debian.org/popcon.php?package=monodoc

> but if we want to remove the monodoc module we'll need to move it
> _somewhere_ (standalone svn module?).

I see the point moving the documentation files to mcs, but why the
tools too? IMHO the monodoc tarball should provide only the
documentation framework, and mono (mcs) would then ship the actual
documentation... Most library packages in debian ship monodoc manual
packages:
http://packages.debian.org/search?searchon=names&keywords=monodoc+manual

But of course a circular dependency must be prevented between mono,
xsp and monodoc... one of the reasons the gtk# frontend was moved to
mono-tools and gtk# docs to gtk-sharp-2.0...

Apropros monodoc, in debian we are working on a better way (packaging
wise) to integrate documentation from non-Mono projects in monodoc:
http://wiki.debian.org/Teams/DebianMonoGroup/MonodocIntegration

>   - Jon
>

-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey at meebey.net  http://www.meebey.net/
PEAR Developer    meebey at php.net     http://pear.php.net/
Debian Developer  meebey at debian.org  http://www.debian.org/