On Thu, 7 Jun 2007, Ladislav Michnovi? wrote: > Hi. > > IMHO if the library is standalone, it has no parent package, the doc > could be in the library package as well. In case it is a subpackage of > something bigger, the doc should be in the parent package. This is a > case of libbzip2-1. The doc files are in the bzip2 package. > If I'm wrong, please let me know. > > Regards Ladislav. > > 2007/6/7, Marcus Hüwe <[EMAIL PROTECTED]>: > > Hi, > > > > I'm trying to build a lib properly according to the "Shared Library > > Packaging > > Policy". According to this document a lib$NAME$NUM package contains only the > > shared object itself. Now I want to add some %doc files (like README, > > COPYING > > AUTHORS etc.) but I'm not quite sure if i can add the the lib$NAME$NUM rpm. > > So where do i have to place the %doc files? (i can't find a similar case > > in the "Exceptions"-section) > > > > Thanks in advance.
Shared library packages can contain documentation as long as it is placed in the default %doc directory (the one that would be called /usr/share/doc/packages/lib$NAME$NUM/). If it is extensive documentation exceeding license, readme and stuff like that a separate -doc package is recommended. That said, the usual case is that with a shared libaray package there comes at least a -devel package which is another appropriate place to put documentation in. Richard. -- Richard Guenther <[EMAIL PROTECTED]> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex
