Board index » delphi » Re: Version Control Advice

2006-04-06 10:51:07 PM
delphi169
because I used that more often (directly, if you see what I mean).
TortoiseSVN is just clunky rubbish.
breaking point, I think.
Cheers,
Jim Cooper
_____________________________________________
Jim Cooper XXXX@XXXXX.COM
Skype : jim.cooper
Tabdee Ltd www.tabdee.ltd.uk
TurboSync - Connecting Delphi to your Palm
_____________________________________________
 

Jim Cooper writes:
interested in diffing files you're primarily working on for changes you
made sometime in the past, you're likely to have all those changes in your
local cache anyway.
Also - BIG ASSUMPTION AHEAD - I am assuming that when you commit your
changes, subversion also synchronizes your cache so you get any history
you missed - all those other developer commits that are not current in
your cache are updated (along with some merge alert?). That way your
diff's are reasonably OK, unless someone was actively working on the same
file recently.
Then again, I am a "don't leave at the end of the day without committing
changes" kind of guy. That comes from a long training on a record-locking
VCS, and if you didn't come in the next day and someone needed your file,
you got beaten about the head & shoulders whenever you dared show up next.
I'd tend to sync my changes fairly regularly.
--
-Brion
There's no such thing as 'one, true way;'
- Mercedes Lackey
 

Matthew Jones writes:
the file w/xcopy or Windows?
I'm honestly trying to see the business case.
--
-Brion
There's no such thing as 'one, true way;'
- Mercedes Lackey
 

Jon Robertson writes:
with Delphi, and I should have been clearer with my wording in the first
place. There are two parts to StarTeam - the server engine, and the
client licenses. The client licenses are definitely Named User, and
portable to multiple machines.
What I thought was against the rules would be to install the server
portion of the software on a separate box. For example, to install the
software that came with my Delphi license on my server at work, and also
install it on my server at home for my personal projects. That seemed to
be the scenario the OP was indicating, and I don't think the StarTeam
bundled license permits this. The client license, however, would be
available for both home and work use, as long as they both hit the same
physical server. Are we saying the same thing now?
--
-Brion
There's no such thing as 'one, true way;'
- Mercedes Lackey
 

Brion L. Webster kirjoitti:
synchronized. And the merge is done, if needed.
David S.
 

Jim Cooper kirjoitti:
David S.
 

Jim Cooper kirjoitti:
in every non-locking system, but then you just have to do the merge by
hand. But I'd never change back to a locked system because of this.
And binaries should be always locked, of course.
David S.
 

clients (TortoiseSvn). You are pre judging a product (SVN) because of a
different product (TorroiseSvn). I quote you "I hate it with a passion.
Vile, disgusting, hard to setup and manage". This you said in a reponse
to "Subversion on the other hand, is simply excellent software.".
Thats like saying that you don't like Delphi because you had a bad
experience with Visual Studio and they both run on Windows.
Befuzeled
Dean
--- posted by geoForum on delphi.newswhat.com
 

Jim Cooper writes:
developer aren't supported, though it is something apparently on the
wish list.
 

David Smith writes:
But, then again, neither does StarTeam. If the repository becomes
unavailable for any reason, the StarTeam client {*word*99}s out. At least,
Version 5.4 does.
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
MedEvolve, Inc
www.medevolve.com
 

On Thu, 06 Apr 2006 10:21:59 +0300, David Smith <XXXX@XXXXX.COM>
writes:
history", and an easy way to sync between main box and laptop.
So far I kinda get the impression that in contrast to most other VCS,
where (from my limited experience) everything revolves around the
repository, Subversion's repository is a bit like scientific journals
ala Nature.
You have a bunch of scientists doing research at different locations.
In order to let the other scientists know what results they've found,
they get an article published in a journal. Other scientists can then,
if they care, read about these results. Or they can go to the archive
and check out results published in earlier issues. Later they
themselfs publish something. If you have two different results from
groups probing the same issue, discussion would occur as to what's
really going on etc.
Subversions repository holds a history of all the previous code
written. It also holds the latest commited code, which you are free to
check out if you want to, regardless of what others do (no locking).
You can also commit code whenever you want to, and if this code
conflicts with what's already in the repository, you need to "settle
the argument", ie merge.
So far, Subversion works ok for me. But I am just myself, so I can
treat the repository in a very different way than if I was working in
a team.
- Asbjørn
 

Brion L. Webster writes:
re-run the SETUP and copy the text out of the "License Agreement" page
of the install wizard. :(
"Under any type of license acquired, for each copy of the Product
licensed by Licensee, Licensee may install one copy of the Server
Software on a single computer. [...] The number of Client Software
copies that may be installed is determined by the type of license
acquired as set forth below"
"2.3 Named User Grant of License. [...] For each copy of the Client
Software, you may install the Client Software on up to five (5)
computers provided that the Named User is the only individual permitted
to use the Product."
my thoughts are in violation of the license or not. My thoughts are
that I can install the "software" on as many computers as I want. I
don't even have to pay for a copy of the software, I can download it
from Borland.
*However*, I can only install a /user/ /license/ on one machine. So if
I install the server at home and at work, I can not install the same user
license on both machines. I would have to have at least two separate user
licenses.
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
MedEvolve, Inc
www.medevolve.com
 

David Clegg writes:
the global working folder. This is what everyone will use unless the
user has specified an "Alternate".
"Alternate" is the working folder for that "user".
Note, however, that it is not really per user, but per workstation. The
alternate folder specified on a given workstation is used for all
StarTeam users that may log into the workstation.
At least, that is how it works for 5.4.
--
Jon Robertson
Borland Certified Advanced Delphi 7 Developer
MedEvolve, Inc
www.medevolve.com
 

Jon Robertson writes:
she wants to dabble in a bit of Delphi in her spare time :-)
--
Cheers,
David Clegg
XXXX@XXXXX.COM
cc.borland.com/Author.aspx
QualityCentral. The best way to bug Borland about bugs.
qc.borland.com
"No, no, no, Lisa. If {*word*62}s don't like their jobs, they don't go on
strike. They just go in every day and do it really half-assed. That's
the American Way." - Homer Simpson
 

Just occasionally I have been doing a load of work on something - a radical
overhaul, and haven't got to a state where I can check it in safely yet.
And then I find it would be nice to see how the files were before I
started. Or need to do a build instantly for a customer's fix. Being able
to create a new folder and in a few clicks get another copy is handy. And
of course you can just delete it again straight away without any
consequence.
/Matthew Jones/
 

Multiple repositories, since it comes up, is another thing I like about
SubVersion. I now have about ten repositories - one for each big project
and some for lots of minor but related projects. They are all accessed
using the same server as they are in subdirectories. But the best thing
about them is they are now all independently backupable and restorable.
And that also means that if one of them needs to move to another person's
server, I can just give them that sub-directory and they just slot it in
on theirs. How you'd do that with some of the competition I just don't
know. I know it wouldn't be possible with the two other VCS's that I use
(and am phasing out).
/Matthew Jones/
 

who does work with us travels a lot, and often codes in a hotel somewhere
and may not have a connection to the internet. The ability for him to code
knowing that he can merge effectively means that he will not now lose time
if he didn't lock a file, and I won't lose time if he's got a file locked
I need to work on.
It is another of the facilities I thought would be odd, having always used
a locking system, but it is working well. And of course you can now use
proper "locks" if you want to.
/Matthew Jones/