From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Charles Wilson" <cwilson@ece.gatech.edu>, <cygwin@cygwin.com>
Subject: Re: RPM 4 under cygwin
Date: Wed, 19 Dec 2001 13:47:00 -0000 [thread overview]
Message-ID: <065701c188d6$521b1510$0200a8c0@lifelesswks> (raw)
In-Reply-To: <3C20BBD0.3030502@ece.gatech.edu>
----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
> Since Larry didn't touch this, I'll respond. Cygwin packages can be
> unpacked/interpreted/understood by a NON cygwin program (setup.exe is
a
> native windows app). ALL ports of RPM that I have seen require cygwin
> -- which means they cannot easily be used to install cygwin itself on
a
> virgin system. This is a serious drawback.
And cannot replace in-use files. AFAIK only my alpha experiment on that
is around for the cygwin/rpm/deb world.
> Signature validation is a good idea(*) -- Robert, can you add that to
> the wishlist?
>
> (*) I'm thinking more in terms the md5 file verification, not
> necessarily maintainer-signature PGP verification...
I can't figure out why it's not there already. I could have sworn...
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 prev parent reply other threads:[~2001-12-19 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 6:20 Jean-Michel POURE
2001-12-19 7:44 ` Larry Hall (RFK Partners, Inc)
2001-12-19 7:54 ` Prentis Brooks
2001-12-19 8:10 ` Jean-Michel POURE
2001-12-19 8:28 ` Larry Hall (RFK Partners, Inc)
2001-12-19 8:11 ` Charles Wilson
2001-12-19 13:47 ` Robert Collins [this message]
2001-12-20 0:47 ` Jean-Michel POURE
2001-12-20 0:47 ` Robert Collins
2001-12-20 1:10 ` Charles Wilson
2001-12-20 1:44 ` Robert Collins
2001-12-20 1:45 ` Robert Collins
2001-12-20 3:02 ` Jean-Michel POURE
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='065701c188d6$521b1510$0200a8c0@lifelesswks' \
--to=robert.collins@itdomain.com.au \
--cc=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.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).