On Tuesday 14 of October 2008, 07:40, Jakub Bogusz wrote: > On Tue, Oct 14, 2008 at 02:35:29AM +0200, Tomasz Pala wrote: > > On Mon, Oct 13, 2008 at 18:29:51 +0200, Jakub Bogusz wrote: > > >> > 2. Why %doc macro puts documentation files > > >> > in /usr/share/doc/%{name}-%{version} directory instead > > >> > of /usr/share/doc/%{name} ? > > > > [...] > > > > > Ability to install new version of package (usually library) without > > > removing old one. This "ability" breaks well known convention that documentation should be placed in `${datarootdir}/doc/${PACKAGE}' (according to `info automake': 2.2.3 Standard Directory Variables)
Some programs have internal help, howtos, manual, etc viewers. These viewers rely on ${datarootdir}/doc/${PACKAGE} documentation location. I'm not going to fix such every program because of broken PLD packaging scheme (even such fixes are trivial). There is other issue - %doc macro should only do one thing - mark files as documentation - unfortunately it does 3 things at once: marks files as docs (this is OK), compress documentation files (it is not always desirable) and copy files to %{_defaultdocdir}/%{name}-{version} (it is most confusing and harmful for me). IMHO %doc macro should accept some options for better controlling its behavior. > > > > After initial mail I've checked my system - none of multiple version > > libraries I have had installed ship %doc. Non-library packages would > > almost certainly conflict on other files. > > Currently on my system (conflicting packages skipped): > libmpcdec-1.2.2-1.athlon > libmpcdec-1.2.6-2.athlon > libstdc++-4.1.2-1.athlon > libstdc++-3.3.6-1.athlon -- Tomasz Wittner _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en