From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Nicholas Wourms" <nwourms@yahoo.com>, <cygwin@cygwin.com>
Subject: RE: Setup as recommended reading
Date: Mon, 27 May 2002 02:01:00 -0000 [thread overview]
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C616A@itdomain003.itdomain.net.au> (raw)
> -----Original Message-----
> From: Nicholas Wourms [mailto:nwourms@yahoo.com]
> Sent: Monday, May 27, 2002 5:12 AM
> To: Robert Collins; cygwin@cygwin.com
> Subject: RE: Setup as recommended reading
>
>
> Hi,
>
> Before you do bow out, I think people need to realize, as it
> was stated before, that you are not trying to reinvent the
> wheel. Yes, RPM is great for many things, but the goal of
> setup isn't to be rpm. In fact, IIRC it was stated that once
> someone had volunteered to support rpm for Cygwin and it was
> proved stable, there might be some discussion as to making
> setup.exe based on the rpm api. There has been some
> discussion lately regarding this port and I believe someone
> has even volunteered to do it.
Yes. In fact both rpm and have been -partially- ported to cygwin. AFAIK
neither has been converted to deal with in-use-file-replacements, which
is a required capability to be a cygwin-linked installer (for somewhat
obvious reasons).
> Be that as it may, it will still be much time before this is
> implimented, IF it is implemented. So let Rob actually
> perfect what he has before asking for heaps of new features.
> IMHO, setup seems to be working nicely for the most part,
> minus a few bugs here and there. I honestly think there are
> more critical issues to focus on then the "fluff" of UI, such
> as getting a fast, stable SysV IPC system integrated into
> cygwin and releasing an updated binutils with better dynamic
> library capabilities.
> Feel free to disagree....
The installer is fairly complete. Howeever I really want to make it easy
for maintainers, so allowing the use of the debian build tools, or the
rpm build tools is a high priority. Otherwise the maintainers here will,
by necessity, end up inventing the wheel.
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-05-26 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 2:01 Robert Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-26 13:47 Robert Collins
2002-05-26 18:19 ` Nicholas Wourms
2002-05-26 12:11 Robert Collins
2002-05-26 9:05 Dockeen
2002-05-26 8:59 Robert Collins
2002-05-26 11:57 ` Brian Gallew
2002-05-26 12:13 ` René Møller Fonseca
2002-05-26 6:30 Robert Collins
[not found] <30C9E24891FFD411B68A009027724CB74433DD@eg-002-015.eglin.af .mil>
2002-05-22 11:55 ` Larry Hall (RFK Partners, Inc)
2002-05-22 9:31 Keen Wayne A Contr AFRL/MNGG
2002-05-26 0:55 ` Jim.George
[not found] ` <Pine.CYG.4.44.0205251652540.1876-100000@gateway.GEORGE.CO. UK>
2002-05-26 0:58 ` Larry Hall (RFK Partners, Inc)
2002-05-26 5:20 ` Christopher Faylor
2002-05-27 6:24 ` Jim.George
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FC169E059D1A0442A04C40F86D9BA7600C616A@itdomain003.itdomain.net.au \
--to=robert.collins@itdomain.com.au \
--cc=cygwin@cygwin.com \
--cc=nwourms@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).