This is the mail archive of the
mailing list for the Cygwin project.
Re: cygport limitations (was: Adding MSYS functionality to Cygwin)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 20 Jun 2013 20:10:56 +0200
- Subject: Re: cygport limitations (was: Adding MSYS functionality to Cygwin)
- References: <CABEPuQJDLjtbcLig1isTUJgb6RBCD8LNShbm9mTPcb9WM5S5fw at mail dot gmail dot com> <51C0B08E dot 8080900 at etr-usa dot com> <CABEPuQJJpRfPKSwZ7M0eTOdp1HxDcmvuy1=qXFHBw-8kLkZ1ZQ at mail dot gmail dot com> <51C0D956 dot 4090905 at etr-usa dot com> <51C1B299 dot 1000701 at cwilson dot fastmail dot fm> <51C1F0F9 dot 70601 at etr-usa dot com> <51C1FA8E dot 3000307 at users dot sourceforge dot net> <51C33F38 dot 4080103 at etr-usa dot com>
- Reply-to: cygwin at cygwin dot com
On Jun 20 11:43, Warren Young wrote:
> On 6/19/2013 12:38, Yaakov (Cygwin/X) wrote:
> >On 2013-06-19 12:57, Warren Young wrote:
> >>You're not talking about anything different than the sort of thing
> >>Cygwin package maintainers go through, sometimes needing to arm-twist
> >>odd build systems to behave according to cygport's expectations?
> >I think you mean Cygwin's expectations?
> Not really, no.
> My point is, cygport's default assumptions about how software gets
> built and installed aren't always correct. Sometimes it has enough
> flexibility to cope with those differences (e.g. my doxygen case)
> and other times it's just not worth the bother (e.g. my ctags case).
My point is, it's always worth to switch packages to cygport:
- cygport is the closest we have to a unified build system (like rpm).
If every maintainer would use cygport, it would allow us to change
the build method to one along the lines of most Linux distros.
In Linux distros, the maintainer provides only the spec file and
the source archive. The actual build for all supported platforms
could be done on a machine which creates the distro from there.
- Cygport does cope with most problems you can come up with and if
it doesn't, you can tweak it. Your ctags problem could have been
easily solved by the lndirs method, for instance. And if cygport
still doesn't cope, there's an active maintainer and a cygwin-apps
mailing list for questions.
- Cygport is pretty easy to use and other people can easily pick up
your package and build another version using your Cygwin build
settings, or even take over maintainership should the need arise.
Of course, the better is the foe of the good, but unless somebody comes
up with another build system which integrates nicely into Cygwin and is
easier to use than cygport, cygport is the best system we have and I
advocate for using it throughout.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple