[Xastir-dev] Hypothetically speaking...

[Curt, WE7U]

On Wed, 10 Nov 2004, Owen DeLong wrote:

> In the past, I have seen this handled by one of several methods:
>
> 1.	Save a revision to db.h that contains only a comment
> 	to the effect that db.h was deprecated and renamed
> 	to <whatever it's now called, I xuggest xaster_db.h>,
> 	then deprecate the file. WIth the new file containing
> 	an initial version that is identical to the last useful
> 	version of the old file and a reference to the deprecated
> 	file for change-log purposes, or, comments that include
> 	the deprecated change log.
>
>
> 2.	Move both the file and the CVS/RCS archive to the new
> 	name so that except for comments to the contrary, the
> 	files think they were always named by the new name.
> 	(This tends to be the cleanest approach overall).
>
> 3.	Simply accept that you lose the change history and move on.
> 	(not my favorite approach).

Thanks.  I'm the admin on several CVS repositories at work, and have
used method #2 before.

I've already changed it, using method #1 but not with as much
attention to detail as you suggested.  I renamed it to database.h
and then removed db.h, which puts it in the special CVS directory
called the "Attic".  We can get back to it if we need to, but I
doubt we'll need to.  I also have archived versions of every Xastir
release I could find, so I can look things up that way as well.  I
need to write those to CD one of these days.

--
Curt, WE7U			         http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"