Re: [James LewisMoss] Re: [ANNOUNCE] first public, highly experimental verison of xml-core
James LewisMoss (dres@debian.org) wrote:
> >>>>> On Sat, 16 Aug 2003 17:22:15 -0500, Ardo van Rangelrooij <ardo@debian.org> said:
>
> Ardo> James LewisMoss (dres@debian.org) wrote:
> >> Is this the email you lost?
> >>
> >> Jim
>
> Ardo> Yes, thank you.
>
> Ardo> See reply within.
>
> >> From: James LewisMoss <dres@debian.org>
> Ardo> [snip]
> >>
> >> Bugs:
> >> 1) Directory /var/lib/xml-core is not included in package.
>
> Ardo> That's true. It's created in the preinst and removed in the
> Ardo> postrm. Anything wrong with that. I didn't really find
> Ardo> anything about this in the policy doc or the developers
> Ardo> reference. But if there's some de-facto approach for this let
> Ardo> me know. I'm more than happy to comply.
>
> Ah missed that sorry. Then the directory wasn't created as it should
> have been. Sorry don't know the cause.
>
> >> 2) postinst script is not idempotent.
>
> Ardo> I don't understand. Installing the package multiple times
> Ardo> works for me, or is that not what you meant? What's the error
> Ardo> you're getting?
>
> If the postinst script errors out in the middle after adding some
> entries, but without completing it'll continue to error from that
> point on because the update-xmlcatalog script will error trying to add
> a duplicate entry.
Ah, I see. Will look into that.
> >> 3) Don't see a way to add a <nextCatalog> entry to the
> >> /etc/xml/catalog file using update-xmlcatalog.
>
> Ardo> That's true. That is (also per to-be-updated Debian XML
> Ardo> policy) not (yet) a supported feature. I uploaded the package
> Ardo> to unstable, so please file a wishlist when it's official
> Ardo> available.
>
> This seems to me to be a really important feature. In fact after
> xml-core did its work I went after it and did
>
> for i in `locate catalog.xml | grep '^\/usr\/share' ; do
> xmlcatalog --add nextCatalog $i --noout /etc/xml/catalog
> done
>
> To get the entries I had before (I had manually created a catalog to
> make xmllint happy).
Well, now you're in for a little surprise: update-xmlcatalog doesn't use
xmlcatalog. Instead it keeps track of what's in the catalog and rebuilds
the catalog from scratch after each change. So, anything you changed in
/etc/xml/catalog not using update-xmlcatalog will be lost next time it's
run. You cannot mix update-xmlcatalog and xmlcatalog for managing the
same XML catalog files. Use xmlcatalog on your own risk.
Yes, I know this should be documented in more than just casual terms, but
that's on the list of things to do.
I would suggest you build a catalog using update-xmlcatalog for your current
things and add that to the root catalog again using update-xmlcatalog.
Thanks,
Ardo
--
Ardo van Rangelrooij
home email: ardo@debian.org
home page: http://people.debian.org/~ardo
GnuPG fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9
Reply to: