cygport: variable package names

Corinna Vinschen
Fri May 4 22:27:00 GMT 2012

On May  4 15:34, Yaakov (Cygwin/X) wrote:
> On 2012-05-04 03:37, Corinna Vinschen wrote:
> >Yaakov, Ping?
> >
> >my workaround has a problem, see below.
> Yes, because the P* variables aren't set that early.
> >Therefore it would be nice if we could get some official method to
> >set package-relevant variables in a pre-package stage, like I asked
> >for in my original mail:
> I'm not sure this particular technique is a good idea, because there
> are other consequences of an ABI version bump; the first of which is
> that other .hint files for that package must be adjusted.  Your
> method could easily cause one to miss those changes, which would
> lead to broken installations.

I understand your concern, but on the other hand the current method
also has a downside.  The creator of the cygport file has to specify
the runtime name including the ABI version as a fixed string.  First
of all, there's a chance that the package creator just doesn't know
beforehand which ABI version will be generated by the package.  And
second, since the ABI version is just hardcoded in the cygport file,
there's also a chance that the package maintainer misses the ABI version
bump and creates a package "libfoo1", while the DLL in the package is
called cygfoo-2.dll.

I think that, either way, you have to rely on the diligence of the
maintainer.  Allowing to automate the package naming and dependency
generation in the package stage, rather than in the install stage,
would at least ease the job, IMHO.

> That being said, I'll think about this further.


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

More information about the Cygwin-apps mailing list