[rt-devel] hacking on rt.

[Jesse Vincent]

> Sorry this is so long.

That's exactly what I needed. It's more that aegis docs are a little hard
to deal with sometimes and it is a _much_ more complex system than CVS with
a fairly different mindset, which requires some serious work to wrap one's head
around fully.  I guess the one thing that still doesn't seem easy
is to provide anonymous read-only access to the live repository. 

Is the right thing there just to script aedist into a commit hook? 
On the client side, I guess a small perl script that does a wget of the .ae
file and an aerecieve would mostly mimic "cvs update" against a remote 
repository.  Or could a script actually ssh to the aegis server and do an aedist
|aerecieve (on the local host) on demand?    

Is there a nice aegis webui somewhere?


Thanks,
	Jesse

> Anyway, these are just my rambling thoughts.
> Others may have much more elegant solutions.
> 
> I hope it helps answer a question or two or, more importantly, spurs a 
> question or two.
> 
> 
> Jesse, thanks again for RT.
> 
> 
> 
> 
> Joshua Johnson
> 
> 
> 
> --On Friday, February 08, 2002 12:20:48 PM -0500 Jesse Vincent 
> <jesse at bestpractical.com> wrote:
> 
> >
> > On Fri, Feb 08, 2002 at 11:02:02AM +0200, Fabian Ritzmann wrote:
> >> Two open-source systems you might want to consider:
> >>
> >> Aegis: http://aegis.sourceforge.net/
> >> - Mature, complete configuration management system. Unix only, but WWW
> >> interface.
> >
> > *nod* I actually spent a bit of time with aegis a while ago and decided
> > that its manual was too obtuse and it was too process-bound.  The fact
> > that it doesn't have a way of allowing remote developers to interact with
> > a repository without local shell access also bothered me.  But over the
> > past day or two, I've been re-familiarizing myself with the package and
> > think I see ways around most of my major issues with a little bit of
> > scripting.
> >
> >>
> >> Subversion: http://subversion.tigris.org/
> >> - Very interesting architecture, but still pre-alpha.
> >
> > A friend of mine hacks on subversion. It looks very interesting, but still
> > isn't quite ready for primetime and it doesn't have one of the two
> > features that I really really want: the ability to do distributed
> > repositories cleanly, so I can work on a branch on my laptop (without
> > net) , checking in every time  I hit a micro-milestone and then merge up
> > to the "main" repository when I  finish.
> >
> >
> > I'm currently leaning toward spending a couple days playing with an aegis
> > repository and the RT 2.1 codebase. The basic plan would be to leave the
> > 2.0 branch in CVS, but to do new development in the new VCS.  Has anyone
> > here worked with aegis?
> >
> > 	-j
> >
> > --
> > http://www.bestpractical.com/products/rt  -- Trouble Ticketing. Free.
> >
> > _______________________________________________
> > rt-devel mailing list
> > rt-devel at lists.fsck.com
> > http://lists.fsck.com/mailman/listinfo/rt-devel
> 
> 
> 

-- 
http://www.bestpractical.com/products/rt  -- Trouble Ticketing. Free.