Endre,
You are correct to observe that directly moving or removing history files (,v files) in the CVS repository causes problems with the existing work copies that users have checked out. Thanks for the heads up.
However, contrary to common belief, the *moved* history files are perfectly functional. They can be checked out from their new location and contain the whole revision history. AFAIK, the problem is really limited to the existing working copies. In the case of log4j, there may be hundreds of such copies thought the world which would all break. Not a good thing (TM).
In order to ensure a smoother transition, one could *copy* the history files to log4j-attic and then perform a *CVS remove* operation on the LF5 files as they exists currently in the log4j CVS repository. This way, we would get rid of LF5 in our regular work environment and still keep its history elsewhere for those who may want it.
Make better sense?
As for the build file, anyone interested in developing LF5 should be able write a target to compile LF5.
At 01:20 PM 9/30/2004, Endre St�lsvik wrote:
On Thu, 30 Sep 2004, Ceki G�lc� wrote:
| | Hello, | | Given that no one is maintaining LF, I have asked whether there was | any opposition to removing LF5 in log4j version 1.3, in a message | posted a few weeks ago. | | There have been no responses. | | I suggest to move LF5 to a new CVS module called log4j-attic. The move | will preserve file history by messing directly with the history files | in the repository. Thus, if anyone decides to resuscitate LF5 in the | future, it would be technically possible. | | Is this OK with everyone?
A comment to moving within CVS: This will most likely kill history for your current project: Will it be possible to check out a snapshot of yesterday's code and build it? Just think about the build-file itself? Won't that have any reference to the lf5-directories, source files or whatever?
Moving in cvs will almost always give you history-breakings, and should as the most general rule always be avoided. What about simply "cvs removing" the files, thus moving them into the actual CVS Attic directory?
Or, I guess, you could convert CVS to a SVN repo, and then do a "move" instruction to it, thus moving the whole dir-structure (which is impossible in CVS) as a history-event.
Endre
-- Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
