public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: cygwin@cygwin.com
Subject: Re: HOW BIG IS IT?
Date: Tue, 20 Feb 2001 12:16:00 -0000	[thread overview]
Message-ID: <3A92CF42.00000017@Enterprise-E.direcpc.com> (raw)
In-Reply-To: <20010220142407.D30769@redhat.com>

At 02:24 PM 2/20/2001, Christopher Faylor wrote:
>On Tue, Feb 20, 2001 at 01:34:55PM -0500, Larry Hall (RFK Partners, Inc) wrote:
> >
> >At 12:54 PM 2/20/2001, Mark Paulus wrote:
> >>Just realize, the size of the package isn't the whole picture.
> >>You also need the space for the download, the space for the unpacking,
> >>the space for the /usr components (man, bin, lib, etc), and the space 
> >>for the "latest" snapshot.  I downloaded what I considered
> >>a base system (didn't include gcc,m4, or any dev stuff except 
> >>make) to a samba disk I have at home.  That took 300 MB or so.
> >>But I tried installing the components I wanted onto a local disk,
> >>and that totally consumed a 900MB disk with it's temp files, and
> >>everything else.  Couldn't even get it installed, until I went to 
> >>a partition with 2+ GB free.  
> >
> >
> >You don't have to download the snapshots.  And you only need to take 
> >"contrib" if there's something you want in there.  Still, I downloaded 
> >"latest" and its 330MB for me ("contrib" is 43 MB).
> >
> >"Is there something wrong with free software that makes it so big?", he asks
> >jokingly.
> >
> >
> >>(Would be nice if setup would allow one to specify whether to keep
> >>packages as they are exploded, where to keep temp files, etc, etc)
> >
> >
> >I doubt you'll get an argument from folks on this list in that regard.
> >Anyone want to patch setup to do this?
>
>The packages are "exploded" into /bin, /usr/bin, etc., AFAIK.  There is
>no need to specify a separate directory for this.  If there are temp
>files they are probably pretty small.


I read Mark's comment as he would like to have setup give you the option to 
remove the package after its installed.  That may not be what he meant.  
You're quite right to point out that there is no intermediate directory
needed for this stuff.  Certainly for anyone using one, there's always 
the option of *not* doing it to save space.


>However, anyone who is really curious about this can check the source.
>I'm not curious at all, so I haven't done so.



Took the words right out of my mouth... ;-)


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2001-02-20 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19  4:37 Andy Canfield
2001-02-19  8:59 ` Earnie Boyd
2001-02-19 15:22   ` Andy Canfield
2001-02-19 20:02     ` Bradley A. Town
2001-02-20  6:20     ` Earnie Boyd
2001-02-20  9:55       ` Mark Paulus
2001-02-20 10:39         ` Larry Hall (RFK Partners, Inc)
2001-02-20 11:24           ` Christopher Faylor
2001-02-20 12:16             ` Larry Hall (RFK Partners, Inc) [this message]
2001-02-21  5:34       ` Cygwin Thanks Andy Canfield

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=3A92CF42.00000017@Enterprise-E.direcpc.com \
    --to=lhall@rfk.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).