Postinstall scripts and file access issues

2004-08-12 Thread Pierre A. Humblet
Those of you that do not follow the Cygwin list should look at the thread http://cygwin.com/ml/cygwin/2004-08/msg00354.html http://cygwin.com/ml/cygwin/2004-08/msg00280.html In brief, postinstall scripts can produce unreadable files, due to interactions between the Windows and POSIX security

Patch for generic-build-script

2004-08-12 Thread Robb, Sam
Attached is a suggested patch for the generic-builf-script. I'm not as familiar with xargs as I should be, so there may be better ways of implementing some of these changes... Areas it affects: - Adds a couple of names to the list of files to be considered documentation (COPYRIGHT, CHANGELOG,

Please update: TeXmacs-1.0.4-3

2004-08-12 Thread Andreas Seidl
Pleas upload the new stable release: http://alice.fmi.uni-passau.de/~seidl/cygwin/release/TeXmacs/TeXmacs-1.0.4-3-src.tar.bz2 http://alice.fmi.uni-passau.de/~seidl/cygwin/release/TeXmacs/TeXmacs-1.0.4-3.tar.bz2 http://alice.fmi.uni-passau.de/~seidl/cygwin/release/TeXmacs/setup.hint and remove the

Re: Postinstall scripts and file access issues

2004-08-12 Thread Christopher Faylor
On Thu, Aug 12, 2004 at 11:04:29AM -0400, Pierre A. Humblet wrote: Those of you that do not follow the Cygwin list should look at the thread http://cygwin.com/ml/cygwin/2004-08/msg00354.html http://cygwin.com/ml/cygwin/2004-08/msg00280.html In brief, postinstall scripts can produce unreadable

Re: Patch for generic-build-script

2004-08-12 Thread Igor Pechtchanski
On Thu, 12 Aug 2004, Robb, Sam wrote: Attached is a suggested patch for the generic-builf-script. I'm not as familiar with xargs as I should be, so there may be better ways of implementing some of these changes... Thanks for the patch. Some comments below. Areas it affects: - Adds a

Re: Postinstall scripts and file access issues

2004-08-12 Thread Corinna Vinschen
On Aug 12 14:18, Christopher Faylor wrote: On Thu, Aug 12, 2004 at 11:04:29AM -0400, Pierre A. Humblet wrote: Those of you that do not follow the Cygwin list should look at the thread http://cygwin.com/ml/cygwin/2004-08/msg00354.html http://cygwin.com/ml/cygwin/2004-08/msg00280.html In

RE: Patch for generic-build-script

2004-08-12 Thread Robb, Sam
Good catch. I'd rather add the '-r' ('--no-run-if-empty') flag to the all of the xargs invocations, though. Told you I wasn't familiar with xargs :-) I really need to spend some time and get more comfortable with it. - When compressing files using gzip as part of an install, adds the

RE: Patch for generic-build-script

2004-08-12 Thread Igor Pechtchanski
On Thu, 12 Aug 2004, Robb, Sam wrote: Good catch. I'd rather add the '-r' ('--no-run-if-empty') flag to the all of the xargs invocations, though. Told you I wasn't familiar with xargs :-) I really need to spend some time and get more comfortable with it. It was actually right there on

RE: Patch for generic-build-script

2004-08-12 Thread Robb, Sam
It was actually right there on the xargs man page... ;-) Ok, so it's settled -- I'll change your patch to do that instead of the -exec option. Just curious - is there a reason to prefer xargs vs. -exec? I know that xargs can be used to avoid shell command line length limits, but are there

Re: Patch for generic-build-script

2004-08-12 Thread Gerrit P. Haase
Hello Igor, On 12. August 2004, Igor wrote: On Thu, 12 Aug 2004, Robb, Sam wrote: [...] - When compressing info files as part of an install, uses the -exec option of find rather than xargs. Packages that already compress info files on install will create an info dir, but there will