On 05/10/11 - 12:16:09PM, Mark McLoughlin wrote:
On Fri, 2011-05-06 at 14:24 -0400, Mike Orazi wrote:
> On 05/06/2011 11:09 AM, Mark McLoughlin wrote:
> > Hey,
> >
> > Before hacking on Aeolus, I wanted to have a dev setup where:
...
> > My notes below. I'd have put them here:
> >
> >
http://www.aeolusproject.org/page/Development_Setup
> >
> > but perhaps this is too sadistic a setup to be generally recommended?
> >
> > Thoughts?
> >
...
> > First up, we need to enable the aeolus RPM repository which we'll pull
> > various dependencies from:
> >
> > $> sudo wget -O /etc/yum.repos.d/fedora-aeolus.repo
http://repos.fedorapeople.org/repos/aeolus/packages/fedora-aeolus.repo
> >
> Probably better to wget:
>
http://repos.fedorapeople.org/repos/aeolus/conductor/0.2.0/fedora-aeolus....
Okay, changed it
> or possibly the not yet existing:
>
>
http://repos.fedorapeople.org/repos/aeolus/conductor/latest/fedora-aeolus...
Yep, that'd be much better
Incidentally, is there any way we can delete some stuff from
repos/aeolus - e.g. packages, packages-testing, demo and puppet?
If you browse that dir at the moment, it's quite confusing to figure out
which is current and which is old cruft
Yeah, it is a good point. Those are exactly the subdirectories that I would
suggest we remove. I'll talk to Mike Orazi today and make sure that is fine
with him.
> Thanks for putting this together. I think it is roughly equivalent to
> what most folks eventually stumble upon for themselves for the isolated
> portion that they care about. Very nice to have a fully comprehensive
> guide & to move it out of the tribal knowledge and into the general eye.
Cheers
> I just noticed that in both your doc & the doc from Justin (cc:ed) the
> old aeolus-fedora.repo file is used. It is fairly inconsequential in
> your docs since you are helping devs get set up and recommend
> installing/running from git anyway. I'm a little worried that some of
> the old rpm deps will get pulled in and never updated for things that
> are outside the direct line of fire (thinking of things like sunspot,
> solr, etc). I"m not sure the best approach to document though, because
> we just moved to a repo layout and I think we may still have a bit of
> work to figure out how things transition from 'testing' to a versioned
> repo (and might also want to add that notion of 'latest-stable' as a
> hard link).
Maybe have development/ and stable/ symlinks? The dev setup wiki page
would reference the former, but the conductor-install.html web page
would reference the latter?
Unfortunately we can't have symlinks. The webserver on
fedorapeople.org
refuses to follow them (I've talked to the admins, and this is a conscious
decision).
My suggestion (and the one that the new layout is following) is to have
released directories (say, 0.2.0) that are frozen in stone, and then a
rolling "testing" that has copies of everything. We can then use hardlinks
to reduce diskspace (there are a couple of utilities out there for doing that).
--
Chris Lalancette