From: Daniel Colascione <dan.colascione@gmail.com>
To: mabrams001@bham.rr.com, cygwin@cygwin.com
Subject: Re: Request for feature: more flexible setup routine
Date: Sun, 25 Jul 2010 04:02:00 -0000 [thread overview]
Message-ID: <4C4BA8D3.8040009@gmail.com> (raw)
In-Reply-To: <30EAF1C130A74F97AC4C82B42ED55DAE@hometoshiba>
On 7/24/10 5:10 PM, Marshall Abrams wrote:
> I have one suggestion: I wish that the setup routine was better for...
> users like me who mainly want to get work done, don't care necessarily
> care whether we have the latest versions of every package (honestly,
> most of package changes are irrelevant to most people most of the time
> (OK, until you need it...)), and more than anything else, don't want to
> break anything that works.
I understand your desire to be conservative, but 1.7 works rather well.
It's not particularly painful, and you can just back up your
installation (perhaps with tar --one-file-system) before trying it out.
Also, keep in mind that you're not required to use Cygwin's package
system. Just as in any other unixy system, can you compile the latest
version of whatever package you need from source and stick the the
result in /usr/local. (I recommend using GNU stow and DESTDIR to keep
everything straight.)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2010-07-25 3:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 2:54 Marshall Abrams
2010-07-25 3:00 ` Christopher Faylor
2010-07-25 20:12 ` Andy Koppe
2010-07-26 11:52 ` Andrey Repin
2010-07-26 12:12 ` Andy Koppe
2010-07-26 15:15 ` Christopher Faylor
2010-07-26 15:19 ` Andy Koppe
2010-07-26 19:25 ` Christopher Faylor
2010-07-27 17:49 ` Andy Koppe
2010-07-27 19:40 ` Christopher Faylor
2010-07-26 19:27 ` Andrey Repin
2010-07-25 4:02 ` Daniel Colascione [this message]
2010-07-25 20:08 ` Jeremy Bopp
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=4C4BA8D3.8040009@gmail.com \
--to=dan.colascione@gmail.com \
--cc=cygwin@cygwin.com \
--cc=mabrams001@bham.rr.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).