From: Paul V. <pa...@vi...> - 2003-09-10 23:16:34
|
Hello all - but especially Tilo this time, We still have those two zips in the CVS tree, and lots of obsolete files and subdirs that should be replaced by the zip contents. One of the zips also unpacks awkwardly, creating a subdir that shouldn't be there at all. We can fix this in two ways: 1. Unpack both zips, moving the contents to the right place where necessary, and commit to CVS. Obsolete files not overwritten by content from the zips can be sent to the attic; obsolete subdirs can either stay in place empty or we must have an admin ask SF to remove them. 2. Repack the troublemaking archive in such a way that it unzips into the right subdir, and leave the two zips in CVS. Move obsolete stuff to attic and/or... same as above. Personally I have a strong preference for solution 1, because a) CVS is a "text thing", and b) unzipping into CVS minimizes the extra steps a body has to take after checking out the manual module. An additional benefit is that if we upgrade the DocBook archives and we have things unzipped in CVS, we can easily use cvs diff if problems arise, to see what has changed, and how, and where. We can't do that with binaries. However, I can live with solution 2 as well. But the present situation makes things unnecessarily complicated. Tilo, what do you think is best? Whichever solution we choose, I volunteer to do the work (or part of it); in fact it'll be a good opportunity to see if my setup works, including committing. Another, smaller thing: Olivier Mascia's path fix should be applied, for those who have Java in a path containing whitespace. I can do that too if you like. After that, all we have to do is write those docs and we're done! :-) Greetings, Paul Vinkenoog PS: "A body" is how Huckleberry Finn says "somebody" or "a person". It just came naturally with the flow of the sentence so I decided to let it stay there. Actually, I think it's really good English! |