If I have a tag such as %PM% in my code, check it in, then check it out
again, I want to see the expanded tag content. In MKS, we had tags such
as ~HISTORY_START and ~HISTORY_END, and when you check in your code and
out again, all the version history lines would be inserted. However, in
Dimensions, the checked out code only has the tag. When you view or
deploy the checked-in version you get the full expanded tag contents.

How can I make the checked-out version look the same as the version
that you get when you deploy? I want to load my under-development
Oracle PSQL code into the development database, and see that it
compiles and outputs the correct version number, without having to
check it in first. What's the point in checking in code that hasn't
been properly tested?

Phil Hibbs.

On 24 Aug 2006 04:06:32 -0700, snarks@gmail.com <snarks@gmail.com> wrote:
....

There's always a good reason to check in code. If I need to do A, B and C to
create feature FOO which then needs to be tested, I tend to check in at
least three times, plus once per bug I find. Makes it easier for me or
someone else to go back and see how it was done (and where it went horribly
wrong).

I hate it when people work on something for weeks and then finally check in
a big lump of unrelated changes ...

As for the keyword expansion, I guess you're not supposed to use it for
anything vital, i.e. you should be confident that whatever they expand to,
the worst thing that can happen is that some version string is not printed.

/Jorgen

--
// Jorgen Grahn <grahn@ Ph'nglui mglw'nafh Cthulhu
\X/ snipabacken.dyndns.org> R'lyeh wgah'nagl fhtagn!

Jorgen Grahn wrote:

Well, failing to compile would be inconvenient. When you check in your
code and keep it checked out for further modifications, you get a local
copy that doesn't have the tags expanded. You have to retrieve the file
read-only to a separate place in order to compile the expanded version
of the code.

Any answers to my problem?

Phil Hibbs.

On 1 Sep 2006 01:29:46 -0700, snarks@gmail.com <snarks@gmail.com> wrote:

I think that was my point -- if you cannot compile without the expansion,
you should fix that (add a test, and make your version output say "private
build by FOO on 1.9.2006" or something if the keyword is absent).

I do such things to CVS keywords; CVS expands $Id$ and such everywhere, but
the much more important $Name$ only appears when you export a labeled
version. I guess that's a parallell to what PVCS does to you.


I have to admit that what I wrote wasn't a solution, in the way you hoped
for. Sorry.

/Jörgen

--
// Jorgen Grahn <grahn@ Ph'nglui mglw'nafh Cthulhu
\X/ snipabacken.dyndns.org> R'lyeh wgah'nagl fhtagn!