RE: cvs commit: xml-fop build.sh

[COFFMAN Steven <SC...@CBSINC.com>]

I don't understand at all. Why would xml-fop/docs/examples/runtests.sh
checkout of CVS with properly set execute permissions, but build.sh will
not? I removed it and then checked in an executable version to do exactly
this and it didn't change anything. Wacky.

Anyway, I haven't been making much progress with Jon Mountjoy's list
indentation (interrupted by end of the page) bug. Fixing this permissions
was just procrastination.
-Steve

-----Original Message-----
From: gears@locus.apache.org [mailto:gears@locus.apache.org]
Sent: Friday, July 14, 2000 3:30 PM
To: xml-fop-cvs@apache.org
Subject: cvs commit: xml-fop build.sh


gears       00/07/14 12:29:45

  Added:       .        build.sh
  Log:
  I'm adding it back with execute permissions turned on.
  This should work in theory.
  
  Revision  Changes    Path
  1.4       +1 -1      xml-fop/build.sh
  
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org

Re: cvs commit: xml-fop build.sh

[Keiron Liddle <ke...@aftexsw.com>]

COFFMAN Steven wrote:

> I don't understand at all. Why would xml-fop/docs/examples/runtests.sh
> checkout of CVS with properly set execute permissions, but build.sh will
> not? I removed it and then checked in an executable version to do exactly
> this and it didn't change anything. Wacky.

An anooying thing I have found with cvs is that if a file is added with
particular sticky tags, then you want to change them (eg. make it a binary
file) and you remove the file and then re-add the file with the binary flag
on the cvs merely recovers the old file from it cvs 'Attic' and does not add
the actual file you added.
This may be related to your exeprience. One way to fix this is to delete the
file from the Attic in the cvs repository (possibly dangerous).