On Tue, 2004-07-20 at 06:50, Michael Schwern wrote:
> There's an important matter of degrees here. Setting CVSROOT and
> running "cvs update" periodically is orders of magnitude less
> complicated than subscribing to a mailing list, setting up procmail,
> PGP and aedist.
You are mixing setup cost with update cost.
The CVS setup cost and the manual CVS update cost are almost identical.
The Aegis setup cost is larger and the manual Aegis update cost is very
small. You update more often than you setup.
Once you have Aegis configured, your large setup cost is amortised by a
zero update cost (zero manual effort, anyways; the machine still has to
do work).
> In my line of work (open source) if there's too much setup involved to
> work on the project most people won't bother. That's why the primary
> mode of development is still mailing patches around, there's a minimum
> amount of work on the part of the volunteer to send in a casual fix.
That's what aepatch -receive is for. Casual developers can still email
the maintainer patches. They email me patches all the time.
Similarly, where project maintainers are NOT using Aegis, as a developer
you can use Aegis at your end and send the maintainer patches. That's
what aepatch -send is for. I did all by GNU Gettext work from within
Aegis and send all my change sets as patches, for example.
--
Peter Miller <millerp@xxxxxxxxxxxxxxxx>
signature.asc
Description: This is a digitally signed message part
_______________________________________________
Aegis-users mailing list
Aegis-users@xxxxxxxxxxx
http://www.auug.org.au/mailman/listinfo/aegis-users
|
