-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "David" == David Brennan <[EMAIL PROTECTED]> writes:
David> We currently use Visual SourceSafe (VSS) which it turns out
David> (after some comparison with other options) is quite nice in
David> terms of core feature set. However is isn't a true
David> database with atomic commits so there is that constant risk
David> of database corruption if a network connection dies. We've
David> been pretty luck so far but we have had one fairly minor
David> scare. It also lacks strong support for branching and
David> changeset type changes.
Hmm, "nice in terms of core feature set", but somehow misses all the
things that are essential to a decent source code control tool :-)
David> So the current favourite is probably Perforce.
I use it, I love it.
David> 1. Does anyone know how to reliably achieve similar shared
David> file between folders functionality in Perforce?
It doesn't have this feature, because it doesn't work. With this
feature you can no longer reliable track changes to a branch or a
product.
David> 2. Most development companies must have similar shared
David> source files. How do you structure your projects and source
David> files? (Note: I am talking about source files used by
David> projects here, not files which are compiled into VCL
David> packages)
I always branch every single library to a product or products
directory. So you know exactly what you've got. You don't have to
recompile (or find out with a full build) that your library update
broke dozens of other projects.
It allows very fine-grained and controlled migrations of libraries.
Read this portion of the SVN handbook:
http://svnbook.red-bean.com/en/1.4/svn.advanced.vendorbr.html
Which explains the concepts.
David> So. what's a developer to do!?
Make sure he can track every single line of code change to a binary.
- --
Cheers,
Berend de Boer
PS: This email has been digitally signed if you wonder what the strange
characters are that your email client displays.
PGP public key: http://www.pobox.com/~berend/berend-public-key.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFG+YzLIyuuaiRyjTYRApm3AKCxj4c3wffA89bH+IhWnSdPyw9JAACgxSkk
4xr35k83n3Iw1c0VsJ2bmek=
=Cu1T
-----END PGP SIGNATURE-----
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi@delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
