Re: [xml] How is xmlcatalog --sgml --del suppose to work?

[Daniel Veillard <veillard redhat com>]

On Sun, Jul 04, 2004 at 09:16:10PM -0500, Albert Chin wrote:
> At present:
>   $ xmlcatalog --noout --sgml --add /tmp/b /tmp/a
> will add
>   CATALOG "/tmp/a"
> to /tmp/b and add
>   CATALOG "/tmp/b"
> to the super catalog.
>
> I really dislike this. It gives no control over which catalog file gets
> modified (and I don't like the super catalog being modified
> automatically). I'd like the operation of xmlcatalog with respect to
> SGML catalogs to be like so:
>   $ xmlcatalog --noout --sgml --add [new catalog entry] [catalog file]
>
> So, the above would add
>   CATALOG "/tmp/b"
> to catalog file /tmp/a, without updating the super catalog. To update
> the super catalog, rerun xmlcatalog with [catalog file] pointing to
> the super catalog file.
>
> At present, the behavior of XML and SGML catalog operations are
> inconsistent. This would make them consistent, though introduce
> backward incompatibility into the new xmlcatalog.

  Hum, this kind of behaviour surprises me but is certainly on-purpose.
That mean changing it will break things, as the SGML support was added
to repace an old SGML tool. I don't think changing the behaviour is
a good idea. Adding a flag to avoid modifying the super catalog sounds
far far more safe, please bugzilla this.

Daniel

-- 
Daniel Veillard      | Red Hat Desktop team http://redhat.com/
veillard redhat com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/