Does it make sense for xml-fop dev'ers to standardize on a particular directory structure for CVS? It seems that this problem might have been averted had Glen used what I was the standard directory structure for xml-fop development: for development purposes it is best if xml-fop builds be built from under the xml-fop/ directory. If so, some sort of "standard" directory structure might be a good addition to the Fop-Dev FAQ.
DISCLAIMER: If this doesn't make sense (me being something of a CVS-newbie), please disregard. I'm not trying to be picky here, just hoping to learn whether this thought process might improve efficiency for [PATCH] submissions. ;-) Christian Geisert said: > Glen Mazza wrote: > [..] >> 2.) My problem with yesterday's file is that the Index >> was "Index: >> xml-fop/src/java/org/apache/fop/render/rtf/rtflib/testdocs/SimpleLists.java", >> but I don't store FOP in an parent directory named >> "xml-fop". >> >> I manually edited all the indices in the patch file to >> just start with "src/java/..." and re-ran from my base >> directory (for me, xml-fop-10), to get it to work. > > The p option of the patch command should take care of this ;-) > (at least the linux version) > > In this case: patch -p1 <coolpatch.diff > > Christian -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
