This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: Pending Packages List, 2003-10-03
On Sun, Oct 05, 2003 at 02:19:43PM +0300, Jari Aalto+mail.linux wrote:
> setup.hint has been added to each. New URLs are:
>
> Base:
> http://tierra.dyndns.org:81/cygwin/libsigsegv/libsigsegv-2.0-1.tar.bz2
> http://tierra.dyndns.org:81/cygwin/libsigsegv/libsigsegv-2.0-1-src.tar.bz2
> http://tierra.dyndns.org:81/cygwin/libsigsegv/setup.hint
>
> devel:
> http://tierra.dyndns.org:81/cygwin/libsigsegv/devel/libsigsegv-devel-2.0-1.tar.bz2
> http://tierra.dyndns.org:81/cygwin/libsigsegv/devel/setup.hint
The packaging looks incorrect to me. The base package as well as the
devel package contain the same files in usr/lib. They should be provided
by only one package.
However, I don't see any sense in splitting this package in a base and a
devel part if the only service provided by this package is a header file
and a static library. If the package provides a shared lib, this could
go to the base package and that would justify the split.
Btw., unfortunately the package uses a too old libtool but I copied the
latest libtool into the source tree between the `configure' and `make' run
and it successfully creates a cygsigsegv-0.dll and a libsigsegv.dll.a then.
> doc:
> http://tierra.dyndns.org:81/cygwin/libsigsegv/doc/libsigsegv-doc-2.0-1.tar.bz2
> http://tierra.dyndns.org:81/cygwin/libsigsegv/doc/setup.hint
Same for the docs. Why splitting if the documentation is for developers
only anyway?
The source package isn't quite as I think it should be. The patch file
contains all the files created by a configure run but the cygbuilb script
runs configure anyway, so why incuding them?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.