Aegis 4.22

Aegis is a transaction-based software configuration management system. It provides a framework within which a team of developers may work on many changes to a program independently, and Aegis coordinates integrating these changes back into the master source of the program, with as little disruption as possible.

This page is hosted by SourceForge: see also the Project and Statistics pages. [ Download | Documentation | Propaganda | Template Projects | Mailing List | Year 2000 | Windows NT | Localization | Reference Sites | Web Interface | Alternatives ]
Got here via a search engine? Have you found the right “Aegis” project?
From 4.22 onwards, even numbered branches are production branches, and odd numbered branches are development branches.
This is the production branch web site. There is also a 4.23 development branch for users who want the latest features and enhancements.

You could support this project with a donation.

aegis, n. a protection or defense [L, from Gk aegís the shield of Zeus]

Documentation
There is extensive documentation available for Aegis, including
a User Guide,
a Reference Manual,
a How To, and much more.
The Documentation page also has links to HTML versions of these documents.
The Propaganda page also carries comparisons and some other documentation.

Getting Started
There are a number of resources available for you:
There is a worked example of the first few change sets of a new project in the User Guide.
There are some Template Projects which can be downloaded and unpacked using one of Aegis' distributed development mechanisms, resulting in immediately working projects managed by Aegis.
OSS developers will be intersted in the simple GNU auto tools example. If your project uses a simple GNU Auto Tools configuration, this example has instructions to quickly get your project working under Aegis.

Distributed Development

The Geographically Distributed Development chapter of the User Guide describes how to use the aedist(1) command to send and receive change sets.
Both of the aepatch(1) and aetar(1) commands may also be used to send and receive change sets. See the Reference Manual for their man(1) pages.
The Working in Teams section of the How To describes a number of ways to distribute projects.
The Template Projects provide a simple way to get a project started quickly and easily. They are implemented using one of Aegis' distributed development methods.
The feed demonstrates how developers can know when remote change sets are available. This particular link is for Aegis itself, but this mechanism is available for your Aegis projects, too, if you choose to turn it on.

Download

The Download has links to the download files.
The BUILDING file in the tarball contains instructions for building Aegis, or you could use the nicely formatted Building section of the Reference Manual.
A number of distributions include Aegis, so it may be possible to download a pre-built binary.
There are problems using Aegis on Windows NT due to a dissonance in security models between Unix and Windows NT. However, it is possible to build a single user version using Cygwin, see the Windows NT page for more information.

Getting Help

There is an aegis-users mailing list, see the Mailing List page for details.
The How To may also be of assistance.
The User Guide explains the model of software development implemented by Aegis.

Reference Sites

There is a page of Reference Sites for you to browse, including contact information.
You may also like to see the list of SourceForge projects using Aegis, which incidentally showcases the Aegis web interface.

GUI Interfaces
There are several projects which are aimed at providing this.
Ages is a GNOME-based front end to Aegis. It provides a comfortable way to access the most common used functions available from Aegis.
AdvantAegis (download it here) is a Graphical User Interface (GUI) to Aegis. AdvantAegis is written in wxPython (python with bindings).
There are some Tcl/Tk scripts in the Aegis source distribution. They cover common activities such as creating and managing change sets. See tkaenc(1) and tkaeca(1) in the Reference Manual for more information.
There is also the Aegis Web Interface for many tasks which mine Aegis' extensive meta-data.

The beautiful graphics on this web site are by Grégory Delattre.

Aegis is written and owned by Peter Miller <millerp@canb.auug.org.au> and is freely distributable under the terms and conditions of the GNU GPL.

There is more Software by Peter Miller at his home page.

This page has been accessed approximately

times since 8-Sep-2006. ::...

免责声明:
当前网页内容, 由大妈 ZoomQuiet 使用工具: ScrapBook :: Firefox Extension 人工从互联网中收集并分享;
内容版权归原作者所有;
本人对内容的有效性/合法性不承担任何强制性责任.
若有不妥, 欢迎评注提醒:

或是邮件反馈可也:
askdama[AT]googlegroups.com

订阅 substack 体验古早写作:

点击注册~> 获得 100$ 体验券:

关注公众号, 持续获得相关各种嗯哼:
zoomquiet

自怼圈/年度番新

关于 ~ DebugUself with DAMA ;-)

	Documentation There is extensive documentation available for Aegis, including a User Guide, a Reference Manual, a How To, and much more. The Documentation page also has links to HTML versions of these documents. The Propaganda page also carries comparisons and some other documentation.
	Getting Started There are a number of resources available for you: There is a worked example of the first few change sets of a new project in the User Guide. There are some Template Projects which can be downloaded and unpacked using one of Aegis' distributed development mechanisms, resulting in immediately working projects managed by Aegis. OSS developers will be intersted in the simple GNU auto tools example. If your project uses a simple GNU Auto Tools configuration, this example has instructions to quickly get your project working under Aegis.
	Distributed Development The Geographically Distributed Development chapter of the User Guide describes how to use the aedist(1) command to send and receive change sets. Both of the aepatch(1) and aetar(1) commands may also be used to send and receive change sets. See the Reference Manual for their man(1) pages. The Working in Teams section of the How To describes a number of ways to distribute projects. The Template Projects provide a simple way to get a project started quickly and easily. They are implemented using one of Aegis' distributed development methods. The feed demonstrates how developers can know when remote change sets are available. This particular link is for Aegis itself, but this mechanism is available for your Aegis projects, too, if you choose to turn it on.
	Download The Download has links to the download files. The BUILDING file in the tarball contains instructions for building Aegis, or you could use the nicely formatted Building section of the Reference Manual. A number of distributions include Aegis, so it may be possible to download a pre-built binary. There are problems using Aegis on Windows NT due to a dissonance in security models between Unix and Windows NT. However, it is possible to build a single user version using Cygwin, see the Windows NT page for more information.
	Getting Help There is an `aegis-users` mailing list, see the Mailing List page for details. The How To may also be of assistance. The User Guide explains the model of software development implemented by Aegis.
	Reference Sites There is a page of Reference Sites for you to browse, including contact information. You may also like to see the list of SourceForge projects using Aegis, which incidentally showcases the Aegis web interface.
	GUI Interfaces There are several projects which are aimed at providing this. Ages is a GNOME-based front end to Aegis. It provides a comfortable way to access the most common used functions available from Aegis. AdvantAegis (download it here) is a Graphical User Interface (GUI) to Aegis. AdvantAegis is written in wxPython (python with bindings). There are some Tcl/Tk scripts in the Aegis source distribution. They cover common activities such as creating and managing change sets. See tkaenc(1) and tkaeca(1) in the Reference Manual for more information. There is also the Aegis Web Interface for many tasks which mine Aegis' extensive meta-data.