From owner-freebsd-ports Mon Jul 22 18:21:34 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0720C37B400; Mon, 22 Jul 2002 18:21:31 -0700 (PDT) Received: from t-mta7.odn.ne.jp (mfep7.odn.ne.jp [143.90.131.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07A0743E65; Mon, 22 Jul 2002 18:21:24 -0700 (PDT) (envelope-from fuyuki@hadaly.org) Received: from hadaly.dyndns.org ([218.46.6.232]) by t-mta7.odn.ne.jp with ESMTP id <20020723012122085.EFAP.2063.t-mta7.odn.ne.jp@mta7.odn.ne.jp>; Tue, 23 Jul 2002 10:21:22 +0900 Received: from hadaly.dyndns.org (localhost [::1]) by hadaly.dyndns.org (Postfix) with ESMTP id C1F32549E; Tue, 23 Jul 2002 10:21:17 +0900 (JST) Date: Tue, 23 Jul 2002 10:21:17 +0900 Message-ID: <86k7nnnss2.wl@hadaly.dyndns.org> From: Kimura Fuyuki To: shige@FreeBSD.org, hrs@FreeBSD.org Cc: henrik.motakef@web.de, freebsd-ports@FreeBSD.ORG Subject: Re: Whats up with share/xml/catalog? In-Reply-To: <87heirzjnx.fsf@pokey.henrik-motakef.de> References: <877kjo95bj.fsf@pokey.henrik-motakef.de> <86wuro2vim.wl@hadaly.dyndns.org> <87heirzjnx.fsf@pokey.henrik-motakef.de> User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI) X-Public-Key: http://www.hadaly.org/fuyuki.key X-Fingerprint: 8D68 1138 1A85 8556 C6A9 274B 2C72 2E56 3AF7 3D89 MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Is there any plan to extend mkcatalog to create the XML catalogs? thanks. At 22 Jul 2002 20:45:06 +0200, Henrik Motakef wrote: > > Kimura Fuyuki writes: > > > > First of all, this is a bad idea IMHO, scince it breaks PSGML and > > > nsgmls for the XML DTDs without a good reason - it would be better to > > > at least have both the XML version and old-style catalogs avaiblable. > > > > The reason is that XML catalog is better for the XML DTDs. > > I disagree, both have their specific advantages. For example, to > maintain semi-automatically an SGML catalog, you don't need any tools > besides echo and grep, basically. But that's not the point. > > From a ports-centric point of view, I think we should try to make as > much software work out of the box as possible. That would probably > mean making both kinds of catalog files available. > > > I hope PSGML implements the XML catalog parser. ;) > > So do I, but right now it doesn't. Neither does NSGMLS, as far as I > know. Both are pretty usefull for working with XML documents. > > > Just a thought for coexistence: > > > > share/xml/catalog.xml (XML catalog) > > share/xml/catalog (SGML catalog) > > I think that would be the best solution, so that software expecting > either format works. I remeber a thread about libxml expecting an XML > catalog at share/xml/catalog by default, so if one cannot easily > convince it to look at catalog.xml instead, it might be better to > choose different names. Also, I'd say for consitency we should put > both kinds of catalogs in share/xsl and even share/sgml, too. > > > > On a more practical note, given that I didn't notice any changes for > > > mkcatalog, how am I supposed to add DTDs that go in share/xml/* to the > > > catalog? Is there a replacement for mkcatalog, or are there new > > > options I didn't recognize? > > > > I don't know any alternatives to mkcatalog. > > > > See textproc/scrollkeeper/pkg-install > > Hm, this implies a BUILD_DEPENDS on libxml. > > If I recall correctly, in the previous thread I mentioned above, > someone talked about implementing a stand-alone tool to update XML > catalogs, that would be quite a nice thing, IMHO. > > Isn't mkcatalog under control of the ports team anyway? Could we > perhaps modify it to include the neccessary call to libxmls > xmlcatalog, later maybe the new tool, so a) nothing changes for ports > that use mkcatalog now, b) it would be easier to update the catalogs > for new ports, and c) we could switch between xmlcatalog and the new > tool without breaking stuff when it's ready? > > Regards > Henrik -- fuyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message