Since the subject of SVN came up I couldn't resist to ask. Presently my
method is to take a snapshot of the project directory to do backup. Easy
and simple to do, and since I'm a one man show it is good enough for me.
But of course there are problems if you need to look into changes in
code, and transferring to another os also is not all that convenient. A
while back I thought about setting up SVN because of the drawbacks, but
since I am not familiar with it, the setting-up and running of it looked
quite complicated. The other major concern that held me back was about
how much disk space an SVN implementation consumes over time as it
grows, and how big a backup of the SVN server data would be compared to
my present method. What are your experiences?
Regards,
George
Felipe Monteiro de Carvalho wrote:
On 3/21/07, Lee Jenkins <[EMAIL PROTECTED]> wrote:
I was wondering what other did to manage cross platform projects?
I mostly use subversion to manage the source code. You will need a
server for that, of course. It´s not hard to set up, I´ve already done
it for internal non-open source projects. For gpl projects I use
source forge´s svn =)
I think that even with only 2 persons on a project, or even only 1
person working on different
operating systems, subversion is a good solution. Further you can see
all alterations later, it´s very convenient.
but it's a pain to port a project over because of unit reference
paths, etc that are different on each platform.
Why are paths different on each platform? A project should normally
work with paths relative to it´s project file directory, this way
paths work everywhere.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
