Bug 591173 - standard location for catalog.xml
standard location for catalog.xml
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: docbook-dtds (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Ondrej Vasik
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-11 11:32 EDT by Rex Dieter
Modified: 2010-05-18 11:10 EDT (History)
1 user (show)

See Also:
Fixed In Version: docbook-dtds-1.0-53.fc14
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-18 11:10:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rex Dieter 2010-05-11 11:32:15 EDT
As it is, docbook-dts put's these in
/usr/share/sgml/docbook/xml-dtd-4.[]-%{version}-%{release}

which can and does change.  kde upstream is working toward using system-provided copies of these (instead of internal copies), so needs an common, standard location for finding these.

Please consider using simply

/usr/share/sgml/docbook/xml-dtd-4.1/
/usr/share/sgml/docbook/xml-dtd-4.2/
/usr/share/sgml/docbook/xml-dtd-4.3/
... etc...

or provide symlinks doing similar.  Most distros seem to already do something like that already... except for fedora.

Thanks.
Comment 1 Rex Dieter 2010-05-11 11:38:14 EDT
I can help implement either solution, if you want.  If so, let me know which approach you'd prefer.
Comment 2 Ondrej Vasik 2010-05-11 16:40:50 EDT
Thanks for suggestion, no need for help - will check what's the "most distros" - this version - release concept was required for buggy post/postun scriptlets in the past, now could be removed - however - symlinks sounds like a good compromise with no risk.
Comment 3 Ondrej Vasik 2010-05-18 11:10:59 EDT
Done without symlinks, looks safe enough ... Built as docbook-dtds-1.0-53.fc14 - closing Rawhide...

Note You need to log in before you can comment on or make changes to this bug.