Re: Dependencies of libraries libc5-libc6 libraries

[Alex Yukhimets <aqy6633@acf5.nyu.edu>]

> Rationale:
> 
>   1) The documentation for foo is there only once in the libfoog 
> package
>      and libfoo has a symlink in /usr/doc to libfoog. Additional 
>      support files (like /usr/lib/tclxxx for David's tcl packages) 
>      are there only once in the libfoog package.
> 
>   2) The manpages for the development package are also included only 
>      once in the distribution, in the libfoog package.
> 
>   3) One might argue that we could create additional package. This 
>      would mean creating two extra packages: libfoo-support for the 
>      common runtime files, and libfoo-dev-support for the common 
>      devel files (manpages, etc...). I don't think adding two extra 
>      packages per library is worth, we already just added two:
> 	bo: 2 packages per library
> 	current hamm: 4 packages per library
> 	hamm with this proposal: 6 packages per library
> 
>   4) The libfoo and libfoo-altdev are *compatibility* package during 
>      the libc5->libc6 transition. Hopefully the final hamm will have 
>      all the old libc5 packages converted to libc6. This means that 
>      the libfoo and libfoo-altdev are unlikely to be installed on a 
>      hamm system.
>      Even if they are installed on a hamm system, it's likely that 
>      their libc6 counterparts are already there, so these additional 
>      depencies are just a minor annoyance.

Hi.

My understanding was that -dev and -altdev packages are conflicting ones.
Why not included all man pages and other documentation in both
of these packages to avoid creating additional ones?

Thanks.

Alex Y.

-- 
   _ 
 _( )_
(     (o___           +-------------------------------------------+
 |      _ 7           |            Alexander Yukhimets            |
  \    (")            |       http://pages.nyu.edu/~aqy6633/      |
  /     \ \           +-------------------------------------------+