Re: Packaging of libraries

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Aug  5 10:34, Chris Sutcliffe wrote:
> I'm working on packaging rtorrent for Cygwin.  To that end it requires
> libtorrent and libsigc++.  My question is, for libtorrent and
> libsigc++, I need to split the dll and the developer packages
> (obviously), but do I also need to split the devel package and
> separate out the documentation?
> 
> For example, I'm thinking:
> 
> libsigc++-2.2.8-1.tar.bz2 (DLL)
> libsigc++-2.2.8-1-devel.tar.bz2 (headers, import libraries)
> libsigc++-2.2.8-1-src.tar.bz2 (source)
> libsigc++-2.2.8-1-doc.tar.bz2 (Required? - HTML documentation, tutorial)
> 
> Please let me know, thank you.

It's your decision as maintainer.  I would suggest a different layout,
though.  You're somehow missing the fact that DLLs have versions and
that you might have to provide a newer version of the runtime package
at one point.  So a layout like this seems to be more prudent:

  libsigc++/
    libsigc++-2.2.8-1.tar.bz2         (HTML documentation, tutorial, etc)
    libsigc++-2.2.8-1-src.tar.bz2     (source)
    libsigc++20/
      libsigc++20-2.2.8-1.tar.bz2     (DLL)
    libsigc++-devel/
      libsigc++-devel-2.2.8-1.tar.bz2 (headers, import libraries)


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat