Greetings, Corinna Vinschen! >> If you ask me, Setup is long overdue for a complete replacement. >> It "don't have" so many things other package managers allow, that I don't >> even >> know, where to start. Meta dependencies? Suggestions? Virtual packages?
> The problem is not that we don't know this, the problem is, as so often, > that we only have a handful of active developers at all, and nobody > having the time nor inclination to work on setup to keep it ahead of > time. Apology again. :( At 5am brain want only one thing. And it's not "writhing comprehensive posts". I was intent on clarifying your point, but brain said "BED!" and legs followed. > Setup was a wonderful idea, way back when it has been created, but the > vintage charm of its Y2K roots are a bit depressing these days. > So, if anybody wants to take a stab at setup and revamp it, feel free. > The only requirements are, it should still be able to utilize the > setup.ini file created on cygwin.com, it should still be able to work > the mirror list provided by cygwin.com, and it should still provide a > GUI and a command line. Everything else is open for renewal. You might add "should be native application" and "should compile with Cygwin provided toolchain". Else it'll be an unbearable nightmare to support. -- WBR, Andrey Repin (anrdae...@yandex.ru) 26.08.2014, <13:49> Sorry for my terrible english... -- 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