Now I'm looking for a source revision control program for the Mac,
something like RCS under unix - I have SourceServer, but I can't seem to
get it to work with THINK Pascal, and I don't know if it can lock files
in and out, etc.
Thanks in advance!
(Gee, what a helpful group you are :) Once I've finished asking these
questions, perhaps I should write a FAQ for comp.sys.mac.programmer? ;)
: Now I'm looking for a source revision control program for the Mac,
: something like RCS under unix - I have SourceServer, but I can't seem to
: get it to work with THINK Pascal, and I don't know if it can lock files
: in and out, etc.
I would love a CVS for the mac however I doubt it will get ported. I also
haven't seen a RCS port.
Pity, them be powerful tools.
P.S. sorry but the stuff with ETO just doesn't cut it. I can't even use it
at home. Imagine trying to use it in a major buisness setting.
P.P.S. I think apple might :) (use the projector database that is..)
>: Now I'm looking for a source revision control program for the Mac,
>: something like RCS under unix - I have SourceServer, but I can't seem to
>: get it to work with THINK Pascal, and I don't know if it can lock files
>: in and out, etc.
>I would love a CVS for the mac however I doubt it will get ported. I also
>haven't seen a RCS port.
SourceServer works fine with SC++ 7.0, although there were terrible
problems with SC++ 6.0. Is Symantec using the old Think Program Manager
with their Pascal product, perhaps?
You might have a look at Voodoo. It does what CVS does and (IMHO) much
and better and offers a "Mac-like" user interface. I attach a short
description of Voodoo.
Christoph Reichenberger, the author of Voodoo
Voodoo (the name stands for Versions Of Outdated Documents Organized
Orthogonally) is a version management tool for the simple and clear
management of projects in which files are created in numerous versions
(variants and revisions). Since Voodoo is capable of managing
arbitrary files, the program can be employed for more than just the
organization of software projects in a narrow sense (program
development). Even the writing of a book, for example, is a project in
which multiple elementary building blocks (the individual chapters,
illustrations, etc.) evolve in various revisions. Using Voodoo can
also pay off here.
Voodoo allows both variant and revision control, and it
manages not only variants and revisions of single files, but
of a whole software project (multi files, multi users,
multi variants, access rights, ...).
The tool offers a neat graphical user interface and is not only
suitable for mere source code control but can handle all
different kinds of files with amazing compression rates:
typical size of delta between arbitrary files
5% (in words: five per cent) !!!!
no matter whether the files are plain text or any other
documents - e. g. MSWord, WriteNow, Canvas, FileMaker ...).
Contrary, if you try to manage non-text-files with Projector
or SCCS you will not get any space reduction.
Voodoo differs from previous source code control systems in its
orthogonal approach to version management. This means that for
every component of a project hierarchy you can not only store
its revision history but also different variants of the same
component.The orthogonal organization of revisions and
variants leads to a much clearer organization that with other
RCS/SCCS-based tools like Projector/SourceServer and others.
A lite version of Voodoo is being distributed on a shareware basis (30 $).
The package included contains VoodooLite 1.5 together with a
readme document and a manual.
You can get the current version directly from our ftp-server at:
ftp.swe.uni-linz.ac.at in /pub/voodoo
The full (commercial) version of Voodoo is being distributed
UNI Software Plus
Fax.: +43 (7236) 37 69
For further information on Voodoo Lite or on the full version
please contact the author:
Christoph Reichenberger Tel: +43-7262-2166
Erlenweg 2 Fax: +43-7236-3338-30
A-4320 Perg, Austria Internet: ch...@unisoft.co.at
The price for a single copy is $ 190.
There are special prices for multiple copies.
Shipping charge for each order is ATS 150 for Europe
and $ 27 outside Europa respectively.
Voodoo differs from Voodoo Lite in the following two major points:
Multiple users and access privileges
Multiple users can be defined for each project.
Each project has one administrator
(the person who created the project).
The management of users, passwords and access privileges
is reserved for the project administrator. Upon selection
of the command File:Define Users! users can be added and
deleted and individual user access privileges can be
assigned. For each user the following settings can be
- User identification and password: The project
administrator assigns the user name and password for each
user. When logging in, the user can change the password,
but not the user name.
- Access privileges to the project tree: Modifications
in the project structure and the variant information are
significant changes in the development of a software
project. They should thus be reserved for selected
persons and not be available to each programmer in the
project. The administrator can specify whether a given user
has access to design mode, i.e., can modify the project
structure and the variant information.
- Access privileges to the project variants: The
administrator can determine which users have which access
privileges to which variants. The possible settings are
write, read-only and none.
All preferences (window positions, filter settings, location of
the local files, etc.) are managed independently for each user.
Whenever a modification to the project is made (storing objects,
changing the project structure or variant info) Voodoo remembers
who made these changes.
In order to ensure integrity of the project data only one user can
access the project at the same time. While a project is open,
Voodoo rejects additional attempts to open the same project and
informs the user about who is currently working on the project.
Voodoo allows the definition of up to 255 project variants
and manages these variants orthogonal to the revisions as
described in the manual.
Every project variant has a name and can be described
further by means of a comment. Each new project contains
by default one variant named "TheOnlyVariant".
The definition of variants is especially useful together
with the filter mechanism.
If a user lacks access privileges to certain variants,
then the project tree shows only nodes of variants to
which this user has at least read-only privileges.
The user is thus not even aware that these variants exist.
Within those variants that are visible to the user based
on access privileges, the user can set variant filters
that further restrict the view of the project. In the
View menu the user sees all variants with at least read
Christoph Reichenberger Tel.: +43-7236-333882
UNI SOFTWARE PLUS GMBH Fax: +43-7236-3769
Softwarepark Hagenberg Internet: ch...@unisoft.co.at
A-4232 Hagenberg, Austria
> I would love a CVS for the mac however I doubt it will get ported. I also
> haven't seen a RCS port.
Check out VersionMaster from AStar Technologies.
PO Box 1100 Littleton MA 01460
__ Michael Peirce __ mpe...@peircesw.com <- New ADDRESS!
__ Peirce Software, Inc. __ 719 Hibiscus Place, Suite 301
__ __ San Jose, California USA 95117-1844
__ Makers of: SMOOTHIE & __ voice: +1.408.244.6554 fax: +1.408.244.6882
__ PEIRCE PRINT TOOLS __ AppleLink & AOL: peirce
> You might have a look at Voodoo. It does what CVS does and (IMHO) much
> and better and offers a "Mac-like" user interface. I attach a short
> description of Voodoo.
You say that Voodoo does what CVS does. Does it mean Voodoo has
`cvs diff' and `cvs patch' functionality?
I did as asked and went and checked out Voodoo lite. I was impressed by
some aspects and depressed at the lack of others. The answers to your
questions are no and no. Furthermore it does not do what CVS does. CVS
stands for Concurrent version system (I believe). CVS allows multiple
developers to "check out" modifiable version and then helps later with
any conflicts created (rare in practice).
Personally my macintosh development currently does not require concurrency.
Thus that aspect is not important. However the lack of an automatic diff
is a big problem I think. Furthermore even if you use Source Server
(Projector under MPW) The compare in a window option is less than usefull.
Yes with both you could checkout two versions and do the diff, however its
messy. I am very familar with diff -C2 output. I parse it like a language.
I want my versioning tool to produce it with command line args. diff -C2
(or whatever options) can then also be used to update sources that others
have (using patch).
The main problem is that the mac doesn't really have any large scale
open source projects. So the need to support diff and patch is minimal
Oh well :)
> I did as asked and went and checked out Voodoo lite. I was impressed by
> some aspects and depressed at the lack of others.
Well we got to hear some of your dislikes. How about some of the
aspects that impressed you?