PCYMTNQREAIYR (Was Re: cygwin packaging approach for atlas3.6and lapack3)

Gerrit P. Haase gerrit@familiehaase.de
Mon Jun 27 10:21:00 GMT 2005

Brian Dessent wrote:

For the record:

> On the issue of not having future binary packages blow away a
> source-compiled optimized version, you could do something similar to how
> the gcc-mingw-* packages work.  Those packages unpack to a single .tgz
> file and postinstall/preremove scripts that extract/remove
> (respectively) its contents to the proper location.  It's an extra level
> of indirection in the packaging. (I'm not entirely sure why this is done
> but I think it is a convenience so that the upstream mingw binary
> tarballs can be used without repackaging.)

Not exactly true, repackaging is still needed for gcc-mingw since the
used paths are different.  The main reason is that extracting the
packages would fail if the directory usr/i686-pc-mingw (and links
inside) is missing, so the postinstall script creates this directory
and links first before the tarball is extracted.


More information about the Cygwin-apps mailing list