[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Adding changeset-like functionality to subversion

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2002-10-09 11:17:12 CEST

On Wed, Oct 09, 2002 at 09:11:52AM -0700, David Mankin wrote:
> On Wednesday, October 9, 2002, at 07:58 AM, Brad Appleton wrote:
>
> >On Tue, Oct 08, 2002 at 03:11:35PM -0500, Ben Collins-Sussman wrote:
> >>http://subversion.tigris.org/files/documents/15/17/svn-
> >>design.html#Repository%20Structure
> >
> >Thanks - that was helpful! I have some questions now about the
> >cloning and repo-wide revision numbers.
> >
> >* so if a particular file does not have its contents change between
> >two subsequent versions of the repository, it seems it still has a
> >different version number for that file (yes?)
> >
> >If so, how do I use svn with more sophisticated build tools like Odin
> >or Cons (which look at not only last-mod times of files, but also
> >their rev-ids and their build command-lines) so that it knows NOT to
> >recompile a particular file if it hasn't "changed" after I updated my
> >workspace? If the file contents didn't change, but the file revnumber
> >did change, what do I tell Cons to use (instead of the rev-id) so it
> >knows not to recompile? (whatever it does, I t should take no more
> >time to do than determine the rev-id, otherwise it impedes my
> >build-time for all builds)
> >
> >
>
> AFAIK, Subversion keeps an md5 checksum of each file in the entries
> file just as it keeps a rev-id. So it would be just as quick (if not
> simple yet without such an interface defined) to pull out the checksum
> and see if it's changed as to pull out the rev-id and see if it's
> changed. Does that satisfy your needs here?
>
> [I don't understand the rest of your email, so I'll leave it to experts
> to answer.]

Well, for any large project I wouldn't want to be reading the entire contents
of every file to create a checksum. Luckily, you shouldn't have to. Within
"svn info path", there is also a Last Changed Revision, which is (strangely
enough) the number of the last revision in which path (or something below
path) changed. It should be possible to use that instead of the RCS style
file revision to see whether a build needs to be triggered.

On this subject, I think now would be a good time to bring up command specific
options again. It would be rely nice IMO to be able to do something like
svn info --url or svn info --lastchangedrev, etc. I'm personally not a fan of
command specific options, but I can't think of a better way to get this type
of functionality.

(/me ducks while the flames start once again)

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • application/pgp-signature attachment: stored
Received on Wed Oct 9 18:18:18 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.