On Sat, Dec 21, 2002 at 02:11:12AM +1100, Jeff Waugh wrote: > <quote who="Sven Luther"> > > > There is already a bug report against libxml2 for this, but apparently the > > libxml2 maintainer does not feel responsible for maintaining a xml > > catalog. > > He's not.
Yes, i guess so. > > So, what would it take to obtain a libxml2 catalog ? > > Note that it is not a 'libxml2' catalogue, it's a system-wide XML catalogue > for every piece of software that requires one. So we would need a repository to put them in and a way for registering/unregistering them, and a way of querying or searching them ? > > Whose responsability is it (the one of the debian developper who chose to > > maintain this package ? What if nobody steps forward, either because > > nobody knows that we need such a thing, or that nobody want take the > > responsability of this package) to package it ? > > Get on the debian-xml mailing list and hurry them up ;) - it's a matter of I really don't have time for following yet another list. > establishing a policy and doing a small amount of hacking. Probably a good > idea to use Red Hat's catalogue bits as a reference implementation, too. Where does redhat put them ? BTW, i don't think closing all the bug reports about this saying it is not in <scrollkeeper, libxml2, ..., insert app of the day which breaks because of it> saying that it is not a bug but a lack of a xml catalog is a good way of urging the debian-xml people to do something about it. Sure it will close the bugs, so the respective maintainers have a clean record, but it does not solve the problem (and may be against the social contract, hiding problems and such). Maybe we should create a xml-catalog virtual package, assign the debian-xml list as maintainer and reassign all such bug against this package ? Friendly, Sven Luther
