You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Fogel <kf...@newton.ch.collab.net> on 2002/12/17 18:17:06 UTC
Re: Version numbers in the sources
Can you give a specific, concrete example of what you wanted to find
out, and the sort of information you expected to find? I don't really
understand the problem you wanted to solve here.
-K
Peter Gervai <gr...@tolna.net> writes:
> Why aren't version numbers in Subversion sources?
>
> I thought that some scripts (tools/ directory comes to mind) have missing
> version header because they're unimportant, were created in 10 minutes and
> is autor had better to do than propset svn:keywords. But I realised just a
> moment before that the whole subversion source tree is one big versionless
> heap of code. There is no way to tell whether the code on my disk is newer
> or older than the one in the repos!
>
> Someone please explain this, or kick me while pointing to the entry in the
> FAQ which explains this. And meanwhile tell the secret method everyone uses
> to decide the relation between an exported file and its pair in the
> repository.
>
> Or if there isn't any, what possibly the reason behind not to use $Id$ in
> the sources? Does it cause compatibility problems? Security risk? ...?
>
> If there's none, then why not $Id$ the sources (preferably the ones
> distributed in source form in the sources, and the others in their
> respective help screens)?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Version numbers in the sources
Posted by Greg Hudson <gh...@MIT.EDU>.
On Tue, 2002-12-17 at 14:42, Greg Stein wrote:
> Right. I find them pretty pointless. If your tarball says -r4223, then you
> know where it came from :-) And the notion of files floating freely around,
> outside the scope of a tarball or unpacked tarball? Rare enough that I don't
> want the bother of an $Id$ tag or somesuch in the code...
Well, if you pull a tarball off the net and then build and install it,
you may not remember six months down the line what the tarball was
named. But, I agree that packaging systems make $Id$ tags less pointful
than they used to be.
On the other hand, putting them in the sources would give the keyword
code a good workout. :) (For instance, if our "svn merge" tends to
generate keyword-related conflicts, we'd find out.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Version numbers in the sources
Posted by "Ketil Z. Malde" <ke...@ii.uib.no>.
Greg Stein <gs...@lyra.org> writes:
> Right. I find them pretty pointless. If your tarball says -r4223, then you
> know where it came from :-) And the notion of files floating freely around,
> outside the scope of a tarball or unpacked tarball? Rare enough that I don't
> want the bother of an $Id$ tag or somesuch in the code...
$0.02:
I often print out things -- it's nice to have a tag identifying the
revision, so I know if and by how much a paper copy is out of date.
-kzm
--
If I haven't seen further, it is by standing in the footprints of giants
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Version numbers in the sources
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Greg Stein <gs...@lyra.org> writes:
> Right. I find them pretty pointless. If your tarball says -r4223, then you
> know where it came from :-) And the notion of files floating freely around,
> outside the scope of a tarball or unpacked tarball? Rare enough that I don't
> want the bother of an $Id$ tag or somesuch in the code...
Yeah, it's unlikely with our .c files.
But I think it could happen (heck, already does happen) with the
standalone scripts in tools/, so maybe $Id$ would be helpful there?
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Version numbers in the sources
Posted by Greg Stein <gs...@lyra.org>.
Right. I find them pretty pointless. If your tarball says -r4223, then you
know where it came from :-) And the notion of files floating freely around,
outside the scope of a tarball or unpacked tarball? Rare enough that I don't
want the bother of an $Id$ tag or somesuch in the code...
Cheers,
-g
On Tue, Dec 17, 2002 at 12:17:06PM -0600, Karl Fogel wrote:
> Can you give a specific, concrete example of what you wanted to find
> out, and the sort of information you expected to find? I don't really
> understand the problem you wanted to solve here.
>
> -K
>
> Peter Gervai <gr...@tolna.net> writes:
> > Why aren't version numbers in Subversion sources?
> >
> > I thought that some scripts (tools/ directory comes to mind) have missing
> > version header because they're unimportant, were created in 10 minutes and
> > is autor had better to do than propset svn:keywords. But I realised just a
> > moment before that the whole subversion source tree is one big versionless
> > heap of code. There is no way to tell whether the code on my disk is newer
> > or older than the one in the repos!
> >
> > Someone please explain this, or kick me while pointing to the entry in the
> > FAQ which explains this. And meanwhile tell the secret method everyone uses
> > to decide the relation between an exported file and its pair in the
> > repository.
> >
> > Or if there isn't any, what possibly the reason behind not to use $Id$ in
> > the sources? Does it cause compatibility problems? Security risk? ...?
> >
> > If there's none, then why not $Id$ the sources (preferably the ones
> > distributed in source form in the sources, and the others in their
> > respective help screens)?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org