From: Jean-Michel POURE <jm.poure@freesurf.fr>
To: cygwin@cygwin.com
Subject: Re: RPM 4 under cygwin
Date: Thu, 20 Dec 2001 00:47:00 -0000 [thread overview]
Message-ID: <200112200844.fBK8iQx13965@www1.translationforge> (raw)
In-Reply-To: <3C20BBD0.3030502@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.
This clearly is a demonstration that cygwin would benefit from a static
compilation option. I know this is not an issue for you all, but ...
Coming back to RPM, this would be so nice to issue this command:
rpm --rebuild --target=cygwin package_name.rpms to compile any existing
apckage for Cygwin.
There are 100 times more Linux developpers than $Windows developpers. Why
to reinvent the wheel with another installation format? Do you really think
you can create a universal format including DEB and RPM? Then you need to
produce more work than the creators of these formats. This is such a
difficult project...
Best regards,
Jean-Michel POURE
--
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-20 8:44 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
2001-12-20 0:47 ` Jean-Michel POURE [this message]
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=200112200844.fBK8iQx13965@www1.translationforge \
--to=jm.poure@freesurf.fr \
--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).