From: "Ed C. Lueless" <ed.c@lueless.net>
To: cygwin-talk@cygwin.com
Subject: Re: Is there a script to remove old packages from local disk
Date: Wed, 17 Jun 2009 15:01:00 -0000 [thread overview]
Message-ID: <20090617150059.GF1401@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20090617131011.GI5039@calimero.vinschen.de>
On Wed, Jun 17, 2009 at 03:10:11PM +0200, Corinna Vinschen wrote:
>On Jun 17 13:54, Dave Korn wrote:
>> Christopher Faylor wrote:
>> > On Tue, Jun 16, 2009 at 06:16:17PM -0400, Ralph Hempel wrote:
>> >> Christopher Faylor wrote:
>>
>> >> <duck>
>> >>
>> >> Wouldn't it be nice if setup knew enough to remove the bz2 files for
>> >> packages that were no longer current?
>> >>
>> >> </duck>
>> >
>> > No need to duck. I think setup really should just delete the files
>> > when it is done with them if you choose "install from internet".
>>
>> Keeping the accumulated older versions cached in the local package dir has
>> saved my skin and/or been a handy source of historical reference material on
>> numerous occasions. So if we're going to add a "tidy up local package dir"
>> behaviour, I reckon it should be governed by another check-box on the final
>> page, alongside the "create menu item" and "create shortcut" boxes.
>
>Since I'm using a local mirror and thus the local download option
>exclusively, this isn't as important to me as an option on the
>installer page to brew some coffee(*) during installation. It would
>be nice(TM) if somebody would add it finally.
>
>
>Corinna
>
>(*) No decaf, please. My hippos tend to sleep too much without caffeine.
Actually, I think that I, like most users, use the accumlated contents of
the files in the download directory to provide a cryptographic hash for
use in protecting some of my sensitive data. If I deleted all of the files
in this directory then the hash would be zero!!! Cygwin really needs to
be more security conscious than this.
I vote NO on remvoing files.
-Ed
--
Ed C. Lueless "Programming since 1972"
ed.c@lueless.org
--
"Ed C. - you are the man!"
-- my boss
--
"There's no such thing as evil. Just excuses that heaven won't accept."
-- Peter David
next prev parent reply other threads:[~2009-06-17 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <80152cdc0906161159r2995c80bl3e0c8ffb1d938103@mail.gmail.com>
[not found] ` <20090616191142.GA25409@ednor.casa.cgf.cx>
[not found] ` <4A3819B1.3000906@bmts.com>
[not found] ` <20090617023402.GB23097@ednor.casa.cgf.cx>
[not found] ` <4A38E76F.5070805@gmail.com>
2009-06-17 13:10 ` Corinna Vinschen
2009-06-17 15:01 ` Ed C. Lueless [this message]
[not found] <4A3940A0.3000606@bonhard.uklinux.net>
2009-06-17 23:23 ` Dave Korn
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=20090617150059.GF1401@ednor.casa.cgf.cx \
--to=ed.c@lueless.net \
--cc=cygwin-talk@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).