This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: setup.exe considerations (was: Doubtful about unison)
- From: Andrew Schulman <schulman dot andrew at epamail dot epa dot gov>
- To: cygwin at cygwin dot com
- Date: Tue, 01 Mar 2011 09:04:40 -0500
- Subject: Re: setup.exe considerations (was: Doubtful about unison)
- References: <ikf9e3$ub2$1@dough.gmane.org> <ikfe1p$f00$1@dough.gmane.org> <ikgf2f$vtm$1@dough.gmane.org> <fggnm61cfbkp0fm6jm0lvrns74bk56bls4@4ax.com> <ikgjlh$tk7$1@dough.gmane.org> <aamnm61uhbmgbrq007c6oag7cd7n9hpdt2@4ax.com> <ikgt6p$ubn$1@dough.gmane.org> <4D6BFD09.8020600@gmx.de> <AANLkTimi6R8MFSH63quHW3EqV4z5ucwtgNEPmCWWfjjc@mail.gmail.com> <4D6CD103.7000303@gmx.de>
> >> Which is the problem: the unison command was compiled against a newer
> >> cygwin1.dll than yours.
> >
> > To be fair, setup.exe ought to be able to resolve or warn about such
> > version dependencies. Unfortunately the infrastructure for that isn't
> > in place, as it would require version requirements to be expressed in
> > packages' setup.hint files (rather than in their READMEs, as they are
> > at the moment).
It would also require packagers to know what the version requirements are.
I can record what versions of things were installed when I built Unison -
or better yet, get cygport to record that for me - but I don't really know
whether it would break with an earlier or later version of cygwin, etc.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple