From: ping <songpingemail@gmail.com>
To: cygwin@cygwin.com
Subject: Re: best way to re-install and keep cygwin configuration
Date: Fri, 13 Jul 2012 15:32:00 -0000 [thread overview]
Message-ID: <50003F84.7020603@gmail.com> (raw)
In-Reply-To: <176672993.20120713050916@mtu-net.ru>
On 07/12/2012 09:09 PM, Andrey Repin wrote:
> Greetings, LMH!
>
>
> Totally unnecessary. If you've maintained your installation for quite some
> time, updating regularly, then setup cache contains lots of obsolete packages.
> Would be much, much faster to just burn it and download new setup.exe when you
> need it.
>
this sound to me that I made a mistake.
I typically when got a new pc, or a new installation of OS, just
download setup.exe
and install "ALL" a/v package, in order to ease the future usage.
but now it typically takes 1 or 2 days to finish, considering also
install cygwin port packages...
I'll install based on a "install-on-need" base...next time.
b.t.w., comparing with a "real" linux, like ubuntu, the current cygwin
package maintenance tool
seems still in the raw stage , comparing with apt-get machanism ... not
to complain..
--
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
prev parent reply other threads:[~2012-07-13 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 18:08 LMH
2012-07-12 20:10 ` Earnie Boyd
2012-07-12 20:28 ` Larry Hall (Cygwin)
2012-07-12 20:31 ` Earnie Boyd
2012-07-12 20:39 ` Larry Hall (Cygwin)
2012-07-12 20:44 ` K Stahl
2012-07-12 21:04 ` LMH
2012-07-12 21:42 ` Larry Hall (Cygwin)
2012-07-13 1:20 ` Andrey Repin
2012-07-13 2:14 ` LMH
2012-07-13 5:53 ` Mark Geisert
2012-07-13 15:59 ` James Johnston
2012-07-13 15:32 ` ping [this message]
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=50003F84.7020603@gmail.com \
--to=songpingemail@gmail.com \
--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).