[SATLUG] Cross Platform Idiocy?

[Travis H.]

On 9/20/06, Justizin <justizin at siggraph.org> wrote:
> FWIW, svn copy is not a bad means of branching.  It's not as good as
> BK, but I find it poignant that perforce actually can't accomplish
> what svn copy does. ;)

I once saw a company who implemented branching in RCS.

Basically they created a version-controlled "meta project" with makefile
that checked out the appropriately tagged versions.

While I think that version control system should be able to handle such
things without a nested invocation, it taught me that I didn't know
everything about source code control.

I used CVS extensively, something like 200 projects (not all mine, some
were tracked versions of open-source code), and it was pretty bad.  SVN
seems to work just fine to me, but I don't branch my own code, I write it
to work on every OS that is appropriate.

If I needed something only on one platform, I'd probably write it as a
seperate library.

> Here's another good point - as happened with BitMover / BitKeeper and
> the Linux kernel, when a commercial entity "graciously" provides you
> with a free license to their tools, they gain some leverage over your
> project with every commit.

Yeah, it's called vendor lock-in, you know, just like the mainframe days.
The thing that open-source on PCs stands against.
-- 
Enhance your calm, fellow citizen; it's just ones and zeroes.
Unix "guru" for rent or hire -><- http://www.lightconsulting.com/~travis/
GPG fingerprint: 9D3F 395A DAC5 5CCC 9066  151D 0A6B 4098 0C55 1484