This is the mail archive of the cygwin-apps@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] |
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. Howabout that? Rob -- GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.
Attachment:
signature.asc
Description: This is a digitally signed message part
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |