This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Re[3]: cygwin download incomplete - try again - loop?


I'm forwarding this to the cygwin list - its generally not a good idea to use
private mail.

I'm a relative newcomer to cygwin - congratulations belong far more to all the
Cygwin maintainers.

Arthur I Schwarz <Arthur_I_Schwarz@raytheon.com> wrote:
> Max;
>
> Sorry. I was talking about the 'null pointer' problem. The fix was to
> download and install from the 'net.

Should be fixed properly as of setup-2.249.2.2

> However, now that we're talking about wishes (or now that I'm going to
> start to talk about the same), what I like to do is to download the sources
> and executable from the net and then install locally. In the process, I try
> to remove old sources and executables so that, at each upgrade, I have the
> minimum amount of data to support the current installation. For me, the
> idea of being able to support different downloads from different sources in
> different directories is a nuisance because after the build I have to
> migrate the files from their downloaded directory to a common directory. It
> is confusing since I can not then do another install because the original
> directories are purged, and I have no idea what to do about the log and
> .ini files. So my wish is that a 'merge' option be made available. The
> merge would:
>
> [1] Migrate all code from the download directory(ies) to some common
> directory.
> [2] The log an .ini files be merged in like fashion.
> [3] Following the merge, it becomes possible to do an install from this
> common branch.

For [1] and [3], Michael Chase has a Perl script called clean_setup.pl which
does this: http://home.ix.netcom.com/~mchase/zip/

As for [2], the log files don't need merging (There are only two sets, one in
the package directory and one in /var/log), setup.inis from the cygwin mirrors
all contain the same content anyway (assuming all the copies of it are up to
date.

If you also download non-official cygwin packages via setup, then I suggest
using the ignore option of clean_setup.pl to ignore those directories. Setup.exe
will dynamically pick up setup.ini files in subdirs of it package cache, so by
leaving the non-official stuff in its own tree, it doesn't muddle up the main
tree.

> Somewhere in the mailing list there is a thread which addresses the
> multiple directories as an issue, and other threads address the 'null
> pointer' problem, the confusion issues, the 'Download incomplete' problem,
> and other things which seem to be incident in the current release.
>
> My frustration is that I am currently trying to change the (local)
> corporate mindset to use Cygwin (and maybe get paid support). I am, oh, I
> don't know, frustrated in that I don't understand the process of
> installation any more. The other day I copied to CD-ROM my 'stuff' and
> attempted to install it onto a WinNT machine. After the 'blue screen of
> death (BSOD), I downloaded all files from a mirror site and completed the
> install. Even at mega-speeds it takes a while to download 4-500 megabytes.

Hmm. If you still have the CD around, please ls -R or dir /s it, and send the
output of one of those commands to me be private mail (no need to spam the list
with that).
What you are trying to do is certainly possible, though.

> And after all this griping, thanks. I can't tell you how many times my
> epidermis was mildly gratified with Cygwin.
>
> art

Max.





--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]