savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers] [ 101121 ] aegis support


From: nobody
Subject: [Savannah-hackers] [ 101121 ] aegis support
Date: Tue, 29 Oct 2002 17:31:16 -0500

Support Request #101121, was updated on 2002-Jul-23 13:33
You can respond by visiting: 
http://savannah.gnu.org/support/?func=detailsupport&support_id=101121&group_id=11

Category: None
Status: Open
Priority: 5
Summary: aegis support

By: yeupou
Date: 2002-Oct-29 23:31
Logged In: YES 
user_id=1896
Browser: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020623 
Debian/1.2.5-0.woody.1

Others questions:

- Is aegis available as an official Debian package?
- If we install aegis and provide it as alternative to CVS,
are you ready to volunteer to maintain this for Savannah &
gnu.org in the long run (basically, the same idea that
http://savannah.gnu.org/faq/?group_id=11&question=Are_PHP_and_MySQL_available.txt
) ?

----------------------------------------------------------------------

By: jmd
Date: 2002-Aug-28 06:36
Logged In: YES 
user_id=5461
Browser: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)

OK.  Here are some of the fundamentals differences between 
aegis and CVS.  Please note I'm not an expert on CVS so my 
info may be out of date and/or plain wrong!

Aegis is transaction based.  That is, every `commit' is 
atomic, whereas CVS is file based (If foo.c gets committed, 
but foo.h is forgotten, then there's trouble).

Aegis enforces  integrity of the project.  It is impossible
to commit something that will break the project.  Examples 
of something `breaking' the project, is a source file that 
will not compile or something that'll cause the program to 
crash.  CVS on the other hand will commit absolutely 
anything that the user requests.

Aegis works in unison with the tools used to develop the 
project.  For example the makefile (or whatever build 
system  and dependency maintenance tool you have).   CVS 
knows nothing about the  build system.

Aegis can work with (almost) any history format (RCS, fhist 
etc).   CVS is reistricted to RCS format.


With a properly set up aegis project, it is impossible to 
misuse.  CVS has `backdoors' which allow arbitrary access 
to the repository.


Some disadvantages of aegis are:

* It is essential that the build system (Makefile) is 
absolutely perfect.

* Essentially useless on WIN32 systems.

* Steep learning curve for novice administrators (but not 
for users).

* Perceived by naive indivduals as introducing unecessary 
complications.




----------------------------------------------------------------------
You can respond by visiting: 
http://savannah.gnu.org/support/?func=detailsupport&support_id=101121&group_id=11




reply via email to

[Prev in Thread] Current Thread [Next in Thread]