Skip to Content.
Sympa Menu

sm-grimoire - [SM-Grimoire] Re: PERFORCE change 13731 for review

sm-grimoire AT lists.ibiblio.org

Subject: Discussion of Spells and Grimoire items

List archive

Chronological Thread  
  • From: "Sergey A. Lipnevich" <sergey AT optimaltec.com>
  • To: Geoffrey Derber <Geoffrey.Derber AT Trinity.edu>, sm-grimoire AT lists.ibiblio.org
  • Cc:
  • Subject: [SM-Grimoire] Re: PERFORCE change 13731 for review
  • Date: Thu, 10 Jul 2003 02:02:02 -0400

Geoffrey Derber wrote:

Sergey A. Lipnevich wrote:

Geoffrey Derber wrote:

2. Attempt to modify libcvs_url to allow MD5s
on the release branch (should never change), then
add the MD5 for the release branch.




I don't think you have to modify anything in url_cvs. If you get sources with specific tag (not just from branch, these change), /and/ the tag is not being moved (some teams do that), your tarball will not change. Only when sources are taken from HEAD or from a branch's tip, they change. Also, soem keyword substitution may hamper checksums, but we're powerless here. I hope I've understood your idea correctly.



The base sources themselves don't change, but the files inside the CVS folders and the .cvsignore files tend to change, still screwing things up



Ah, yes. But what can be done about it? Except for rewriting unpack() to filter out all CVS directories (which is kinda too much if you ask me, because the generation procedure would change as well)?


You wouldn't re-do unpack, you'd redo the creation, to use 'cvs --export' to begin with which would remove all CVS folders, and then do something to rm all the .cvsignore files. That'd be the easiest, but you could only do it on non MAIN / HEAD branches, so it'd require a couple if statements, but it could be done.

I agree with your argument but I don't agree with removing update. First, CVS tags can move. Second, update is actually a cool way of doinf things. I've just updated apr/apr-util/apr-iconv by changing the tag name and making them FORCE_DOWNLOAD=on (and fixing the sorcery in the process). Alternatively, we could do some post-update processing to wring CVS/Entries into format whihc is a)correct b) good for us to checksum. For example, assuming CVS update brings timestamps to "the time of last change to this file", we could replace dates in CVS/Entries with the dates on the respective files. That would bring two checked out copies of CVS sources in full sync on two PCs. Would it?
BTW, I'm mirroring this into SM-Grimoire just in case somebody wants to join in.
Thanks!

Sergey.






Archive powered by MHonArc 2.6.24.

Top of Page