Hi Piotr,
an OpenSource alternative to SCCS is CSSC, both quite ancient though.
Otherwise this might be useful: http://www.subversion.com
Jürgen
-------- Original Message --------
Subject: Re: [Info-Ingres] SCCS for ABF appliactions
Date: Tue, 9 Oct 2007 10:45:56 +0100
From: Martin Bowes <martin.bowes@ctsu.ox.ac.uk>
Reply-To: info-ingres@kettleriverconsulting.com
To: <info-ingres@kettleriverconsulting.com>
CC: "Wiśniewski, Piotr, (ProService AT)" <Piotr.Wisniewski@psat.pl>
References: <2BF9843FE765D311AAFE0008C70D6F4B05F20782@BOF1PROCJON>
CVS could be worth a look.
Martin Bowes
-----Original Message-----
From: info-ingres-bounces@kettleriverconsulting.com [mailto:info-ingres-bounces@kettleriverconsulting.com] On Behalf Of "Wisniewski, Piotr, (ProService AT)"
Sent: 09 October 2007 10:15
To: info-ingres@kettleriverconsulting.com
Subject: [Info-Ingres] SCCS for ABF appliactions
How can one implement source code control system for ABF applications ?
We create a new database and copy all the source code files for every new
app version, which has it's obvious drawbacks. For example every change in
the lower version has to be manually exported into a newer version.
I did a search on www.déjà.com, but haven't found anything promising.
Thanks
Piotr Wisniewski
_______________________________________________
Info-Ingres mailing list
Info-Ingres@kettleriverconsulting.com
http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres
_______________________________________________
Info-Ingres mailing list
Info-Ingres@kettleriverconsulting.com
http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres
As I understand using each of the mentioned tools implies that there is one
app defined in a database and versioning is managed by that tool, so all
source files, form definition files, frame definitions and so on have to be
checked in and out during the development.
What about record definitions based on tables (e.g "r = type of table t") ?
The table structure can change between app versions and if I'm confined to
one application definition in one database then how do I manage such changes
?
Piotr Wiśniewski
-----Original Message-----
From: Emiliano [mailto:emile@iris-advies.nl]
Sent: Thursday, October 11, 2007 7:01 AM
To: info-ingres@kettleriverconsulting.com
Subject: Re: [Info-Ingres] SCCS for ABF appliactions
> Emiliano wrote:
>> SVN doesn't really do distributed very well, and branching/remerging
[quoted text clipped - 3 lines]
>
> 'svn mv' takes care of that pretty well, no?
If the rename is the only thing you're doing to it, yes. If you rename
and change stuff in the file, things get a bit murkier. Svn doesn't
really support renames, under water it performs a remove and an add,
and does some stuff to keep the history intact.
> I'm not a huge fan of Subversion's properties system, but even so it's my
> favorite source control system. I'm used to working in small groups, both
> open source and in-house. It does what I need.
Same here, that's why we use it. But we've pretty much given up on
branching with SVN. Not worth the pain it causes. When we grow to need
brancing/merging, we'll probably buy Team System.
If only git had a graphical client. I don't mind commandline myself,
but the rest of the group can't cope with them.

Signature
Emiliano
_______________________________________________
Info-Ingres mailing list
Info-Ingres@kettleriverconsulting.com
http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres