Setup Log Directories

[Michael A Chase]

----- Original Message -----
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Michael A Chase" <mchase@ix.netcom.com>; "Cygwin-Apps"
<cygwin-apps@sources.redhat.com>
Sent: Tuesday, January 22, 2002 13:09
Subject: Re: setup.exe: Feature frozen now


>
> ===
> ----- Original Message -----
> From: "Michael A Chase" <mchase@ix.netcom.com>
> To: "Cygwin-Apps" <cygwin-apps@sources.redhat.com>
> Sent: Wednesday, January 23, 2002 8:09 AM
> Subject: Re: setup.exe: Feature frozen now
>
>
> > ----- Original Message -----
> > From: "Robert Collins" <robert.collins@itdomain.com.au>
> > To: <cygwin-apps@sources.redhat.com>
> > Sent: Tuesday, January 22, 2002 01:06
> > Subject: setup.exe: Feature frozen now
> >
> >
> > > * log files in the wrong location
> >
> > Are you just saying that '/' may not be the appropriate place?  If so,
> I'd
> > vote for /var/log/setup/.
>
> See my recent reply to 'for the brave' :].

I think the reason for dropping the log files in the setup.exe directory for
downloads is that there may not be any cygwin directories if you are
downloading in a system that doesn't have any cygwin binaries installed.  In
that case, the download base directory would probably be appropriate.  I can
dig around and see what is needed to make that visible when the log files
are written.

Perhaps instead of depending on the operation being performed, a check for
/var/log/ should control which site is written to.  If /var/log/ isn't
present, then write in the download base directory.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.