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]

Re: setup.exe sucks


On Tue, Dec 07, 2004 at 10:50:36PM +0100, Reini Urban wrote:
>Christopher Faylor schrieb:
>>On Tue, Dec 07, 2004 at 10:17:55PM +0100, Marcel Telka wrote:
>>>On Tue, Dec 07, 2004 at 03:48:17PM -0500, Christopher Faylor wrote:
>>>>On Tue, Dec 07, 2004 at 03:37:36PM -0500, Charles Wilson wrote:
>>>>>Christopher Faylor wrote:
>>>>>>I believe that it was always Robert's intention to work towards the use
>>>>>>of a true package manager someday.  That time is now.  I can't take it
>>>>>>anymore.
>>>>>
>>>>>Perhaps it's time to begin work on a native port of rpm.exe -- but to
>>>>>avoid any "where exactly IS /var/lib/rpm before cygwin is even
>>>>>installed" problems, maybe winrpm.exe should store ALL of its stuff in
>>>>>HKCU somewhere.  /usr/lib/rpm/* and all.
>>>>
>>>>I don't think you need a native version of rpm any more than you need a
>>>>MS_DOS version of rpm when you're installing linux.  You do have to have
>>>>something early on that bootstraps what you need, like setup.exe does
>>>>now, but it could always install the cygwin first before it does
>>>>anything.
>>>
>>>... or you could use statically linked rpm.
>
>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.

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.

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?

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]