Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
Message-ID:	<013301c2011b$35e6fb30$ad01a8c0@jj>
From:	"Jon Foster" <jon AT jon-foster DOT co DOT uk>
To:	"Peter Ring" <pri AT ddf DOT dk>
Cc:	<cygwin-apps AT cygwin DOT com>,
	"Markus Hoenicka" <hoenicka_markus AT compuserve DOT com>
References:	<LLEGJLFMJCCMMIIJBIKDIEJCCLAA DOT pri AT ddf DOT dk>
Subject:	Re: New SGML/XML packages
Date:	Tue, 21 May 2002 23:59:49 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4910.0300

Hi Peter,

Thanks for reviewing these packages.

> sgml-base-1.01, xml-base-1.1:
> A bit messy. How are these resources related? If somebody wanted to add
> another bit, how would you release that?

Looking at these packages again, I agree with you that sgml-base and
xml-base had too many miscellaneous DTDs.  I've cut down sgml-base so that
it only contains the catalog tool, the ISO entities, and the HTML DTDs.  All
these are components are essential, and unlikely to change.  I've cut down
xml-base and split it into two - there are now separate xml-char-ent and
xhtml packages.  Since both of these are likely to change, I want them
separate so they are easier to maintain.

> DSSSL and XSLT stylesheets:
> Different versions of stylesheets might need to co-exist, in my humble
> experience. Not easy with this directory layout.
At the point you need to do that, you're going to have to download and
install the packages yourself, rather than using setup.exe.  If you do that,
you can rename the directory and (for DSSSL) fix up the catalog file
manually.

> docbook-sgml-4.1, docbook-xml-4.1.2:
> Why bundle various DocBook versions into one package? They do not depend
> on each other. How do you intend to release forthcoming DocBook 4.2?
The problem is simple: How many packages do we release?  I've proposed two -
docbook-sgml and docbook-xml.  If we do every version as a separate package,
then we have ten different docbook packages.  This seems a little excessive,
and IMHO is also likely to confuse users.

> Please note that the effort to make a directory layout for XML and
> SGML part of the LSB [1] is now continued. There's a mailing list [2].
> The latest proposal is, I believe, at [3] (and it was sorely lacking wrt.
> XML).
I looked at the FHS when I was creating these packages.  It hardly mentions
XML at all, only SGML.  There doesn't seem to be a consensus opinion on XML
in the mailing list archives.

For now, I've complied with the FHS as far as practical - e.g. the SGML
master catalog is in the right place, SGML DTDs are in the correct location.
I hope that it won't be too hard to migrate from my current packages to
whatever the LSB (eventually) decides.

> By the way, the Debian distribution differs in a number of details [4].
Yep, when I was putting these packages together I started off with the
Debian packages.  The install-sgmlcatalog script is borrowed from Debian.

Thanks & regards,

Jon Foster
--
"The knack of flying is learning how to throw yourself at
the ground and miss." - Hitchhiker's Guide to the Galaxy

E-mail: jon AT jon-foster DOT co DOT uk
web: http://www.jon-foster.co.uk/

- Raw text -