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

RE: Re: tagging just a few files

From: Glenn McAllister <gmcallister_at_sapient.com>
Date: 2004-11-25 19:27:52 CET

Remember that you don't have to tag the entire repository; you can
effectively tag a subdirectory that will give you the desired effect.
Assuming your top level repo structure looks like:

/trunk/pgk1
/trunk/pkg2

Do a build on pkg1 and tag it with svn copy:

/trunk/pkg1 -> /tags/pkg1-v1.0.0

Do another build on pkg1 and tag it with svn copy:

/trunk/pkg1 -> /tags/pkg1-v1.0.1

That should give you the effect you want.

Glenn McAllister
Sr. Associate, Technology, Canada| Sapient

 
-----Original Message-----
From: Sunil Shetye [mailto:shetye@bombay.retortsoft.com]
Sent: Thursday, November 25, 2004 1:41 AM
To: kfogel@collab.net
Cc: users@subversion.tigris.org
Subject: Re: tagging just a few files

Quoting from kfogel@collab.net's mail on Wed, Nov 24, 2004 at 12:37:52PM
-0600:
> > I require to tag some files (spread over many directories) from the
> > repository for tracking changes in those files over time. subversion
> > does not seem to have a simple way of doing so. All methods of doing
> > so are either cumbersome or incorrect. Is it possible to add an
option
> > like "--parents" to "svn copy" to ease tagging of specific files?
>
> I guess it depends on what exactly you mean by "tracking changes in
> those files over time". Describe your goal precisely, we may be able
> to help you out more.

My repository contains source code of several packages. Some of the
files are shared. An example:

pkg1:
include/Makefile
lib/Makefile
lib/a.c

pkg2:
include/Makefile
include/b.h
lib/Makefile
lib/b.c

When I build a package, I like to tag the files of that specific
package only. This way, when there is a problem between two versions
of a package, the changes between the two versions can be reviewed.
Something like:

svn diff $REPOS/tags/pkg1-v100 $REPOS/tags/pkg1-v101

Now, here if I tag the whole repository,

a) the above diff will contain changes to files not in that package.
This makes reviewing the changes difficult.

b) changes in the filelist of the package are not visible. For
example, if I add/delete files to/from a package (but not necessarily
to/from the repository!), the above diff will not indicate the change
in package filelist.

New pkg1:
include/Makefile
lib/Makefile
src/Makefile
src/c.c

Please help me on this. Is there a better way to achieve this?

[PARTLY OFFTOPIC:

I also tried keeping the filelist of a package in a separate file and
then monitoring the changes. Something like:

svn diff -r20020:20024 $( cat file-containing-filelist-of-pkg1 )

Unfortunately, this command causes the repository to partly crash when
the package contains more than 60 files or so. I have already reported
this problem for 1.1.0, but there was no relevant response on this.

<http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=20325>
<http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=20362>

Anyway, this technique does not work correctly when the filelist of
that package has changed between the two revisions.

]

-- 
Sunil Shetye.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 25 19:30:31 2004

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