This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tue, Dec 07, 2004 at 10:50:36PM +0100, Reini Urban wrote:But rpm doesn't handle Recommends and other UI interactions other UI packagers offer. But better than nothing or our current setup.ini.
That's right. RPM does not have Recommends, and that would be nice. It isn't designed to be UI based, though.
At least yum can be used then. I already prepared a yum package, but didn't finish proper testing.
Yes, once we had yum, we could almost have the unattended install working. Of course, you couldn't use yum to install python or cygwin, as it stands right now.
... or you could use statically linked rpm.
Btw, in case my "Sigh" wasn't clear, you can't produce statically linked binaries right now with cygwin and I'm not really interested in getting things working that way. You'd still have the same issues with multiple cygwin DLLs that you do now. It would just be harder to detect.
Scenario: cygwin.com "Install Cygwin now" => cygwin.msi or setup.exe => Dialog dependent on the existing setup:
A year or so ago someone triumphantly announced that they had produce a way to bundle the cygwin DLL (or any DLL) with an application so that there was no need to have two separate files. Anyone remember that?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |