This is the mail archive of the
mailing list for the Cygwin project.
Re: Pending setup patches (issue 2)
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Robert Collins <rbcollins at cygwin dot com>
- Cc: cygwin-apps at cygwin dot com
- Date: Mon, 10 Mar 2003 00:03:01 -0500 (EST)
- Subject: Re: Pending setup patches (issue 2)
- Reply-to: cygwin-apps at cygwin dot com
On 10 Mar 2003, Robert Collins wrote:
> On Wed, 2003-03-05 at 11:52, Igor Pechtchanski wrote:
> > On 5 Mar 2003, Robert Collins wrote:
> > > Other than that, please expand to address all scripts.
> > > Rob
> > Rob,
> > There is a design issue here that I'd like to address before I work more
> > on this. I recall your comment that this should be tied into the logging
> > subsystem. Unfortunately, this would involve a much more complex code,
> > with pipes and forks. The same is true if we want "tee"-like behavior,
> > i.e. windows popping up *and* output going to a file. The way this is
> > implemented now is the output stream of the script process is tied to a
> > file, but the limitation is that the file is written right away. Do we
> > want a more complex design now, or should I just allow running a generic
> > script with output going to a file (for the moment)?
> > Igor
> Hmm, I'd like the following idiom:
> generate to a file.
> copy the file into the log buffer.
> That will get the postinstall scripts into the log.
> How about that?
Sounds fine. I got the first part mostly done (it'll be a "run script,
output to file" idiom). The second might take some time... I'll probably
have to use mktemp() or something similar.
|\ _,,,---,,_ pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`' -. ;-;;,_ igor at watson dot ibm dot com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!