On Tue, May 10, 2005, Michael Schloh wrote:

> On Tue, May 10, 2005, Thomas Lotterer wrote:
> > On Tue, May 10, 2005, Matthias Kurz wrote:
> >> On Tue, May 10, 2005, Michael Schloh wrote:
> >>>   %doc (RPM feature): describes a file as optional documentation
> >>>   %docdir (RPM feature): describes a directory as containing documentation
> >>>   with_doc (OpenPKG feature): inconsistent option which should be removed
> >>>   $ openpkg rpm -qd <pkg> (qd is RPM feature): list documentation
> >>>
> > Close to how I understand it. But there is an important thing missing
> > here. The RPM feature controls the installation of documentation files
> > from the binary RPM into the filesystem. The OpenPKG feature with_docs
> > controls the inclusion of documentation files from the buildroot
> > into the binary RPM. [...]
> >
> Then there are three choices:
> 
>   #1 Supply each package containing docs with a 'with_docs' option
>   #2 Supply only packages with new dependencies with a 'with_docs' option
>      - Others install docs or not dependending on --includedocs as usual
>   #3 Never supply a 'with_docs' option, only installing docs when no
>      dependency problems arise (due to generation for example)

I would prefer #3, when this also means to use %doc(dir).

> >>>   2. Do we package absolutely all vendor docs even when they overlap?
> >>>
> > Once we start I recommend putting in everything we can grab. Sometimes
> > even 3rd party docs like HOWTOs etc.
> >
> And if it gets too sloppy (diverging structures) or heavy (storage)?

Also "external" docs are not versioned. When one fetches before packaging,
then there could always be another doc version. I guess this case is also
catched by the "too sloppy" argument. BTW, there is still the wiki...

> >>>   3. Where do the docs go?
> >>>
> > Or maybe a new "toplevel" dir using %{l_prefix}/doc/<package>/<here>
> >
> Your idea is already in the OpenPKG sources. From rpmmacros:
> 
>   %l_docdir  %{l_prefix}/doc

This would have the advantage, that %docdir would be constant for all
packages. BTW, i think, %docdir works as i expected, i just stumbled
over the first sentence under
   
http://www.rpm.org/max-rpm-snapshot/s1-rpm-inside-files-list-directives.html#S3-RPM-INSIDE-DOCDIR-DIRECTIVE
Now, when there where a dedicated doc hierarchy, how could one forego the
definition of %doc/%docdir in the %files-section at all ? I tried to set
"DocDir: %{l_docdir}" in a .spec, but this did not work as expected.

And how could this all be decided, so that we can go on ? Should there be
a voting ?


   (mk)

-- 
Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47
  >> Im prämotorischen Cortex kann jeder ein Held sein. (bdw) <<
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to