public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@syncretize.net>
To: "'Max Bowsher'" <maxb@ukf.net>, <cygwin@cygwin.com>
Subject: RE: Crashing setup.exe
Date: Fri, 07 Jun 2002 08:55:00 -0000	[thread overview]
Message-ID: <009c01c20e37$d925d2c0$0200a8c0@lifelesswks> (raw)
In-Reply-To: <026a01c20e37$25a362d0$42a18c09@wdg.uk.ibm.com>



> -----Original Message-----
> From: cygwin-owner@cygwin.com 
> [mailto:cygwin-owner@cygwin.com] On Behalf Of Max Bowsher
> Sent: Saturday, 8 June 2002 1:23 AM
> To: cygwin@cygwin.com
> Subject: Re: Crashing setup.exe
> 
> 
> robertc <robert.collins@syncretize.net> wrote:
> > No. One SHOULD NOT TOUCH the cygwin packages directory. 
> Setup reserves
> > the right to do -anything- it wants to that dir, including 
> zapping the
> > content, moving files etc etc.
> 
> Setup has the right to use its package cache as it sees fit, 
> but users of setup
> have the right to manage setup's use of their hard disc. If 
> everyone treated
> package directories opaquely, they would never purge old 
> versions of packages,
> and sooner or later, we would all have 10GB package 
> directories. The setup's
> handling of its cache should be like the rest of cygwin - if 
> you don't like it,
> make a clean, debugged patch to change it, and provide a good 
> argument to why it
> should be applied.

Agreed. 
 
> I appreciate you are trying to prevent aimless discussion, 
> but setup's cache
> _cannot_ be a black box.

I realize this. In fact it's not - and I've not suggested it be a black
box... There are other bits of software - like the setup cache cleaner -
that are very useful. They are intimately linked with setup's treatment
of the cache however, and will have to change as it changes. What I'm
trying to avoid is setup.exe's users getting the impression that there
is any manipulation needed for setup to operate correctly.

Finally, until 'someone' has time to document the exact use of the
cache, it will be a black box to Joe User, until Joe User reads the
code.

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/

  reply	other threads:[~2002-06-07 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07  5:55 fergus
2002-06-07  6:46 ` Pavel Tsekov
2002-06-07  8:13 ` robertc
2002-06-07  8:51   ` Max Bowsher
2002-06-07  8:55     ` Robert Collins [this message]
2002-06-07 10:56       ` Max Bowsher

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='009c01c20e37$d925d2c0$0200a8c0@lifelesswks' \
    --to=robert.collins@syncretize.net \
    --cc=cygwin@cygwin.com \
    --cc=maxb@ukf.net \
    /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).