Re: aenf'ing symlinks
David A Vincent <[email protected]>
| Newsgroups | gmane.comp.version-control.aegis.user |
|---|---|
| Message-ID | <[email protected]> |
On 20/02/2012, at 12:00, [email protected] wrote: > Date: Sun, 19 Feb 2012 00:50:45 -0500 > From: Aryeh Friedman <[email protected]> > To: aegis-users <[email protected]> > Subject: [Aegis] aenf'ing symlinks > Message-ID: > <CAGBxaX=9mBFFvYFsUGF0-P4ShqNj=MHKv6V0_U=Xy24+adxOrw@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I want to centralize all my build/aegis config files for all projects > so for example the standard aegis.conf might be /home/aegis/aegis.conf > but when I do: > > ln -s /home/aegis/aegis.conf aegis.conf > aenf -config aegis.conf > > I get: > > aegis: appending log to "/home/aryeh/b-Common.C010/aegis.log" > aegis: project "b-Common": change 10: path "aegis.conf" is not within > any change or > project directory tree; maybe the -base-relative option will help > aegis: project "b-Common": change 10: found 1 fatal error, no new files added Might be a silly approach, but what if you aenf a copy, then have the project's build script fail unless the copy in the change matches your central version. Repeat for all projects. Then, whenever you changed the central version, all the projects referring to it would want a change to update their copies before other changes could go ahead. -- David A Vincent [email protected] 0404 985 493