On Tue, 2007-11-06 at 00:53 -0800, Erick Tryzelaar wrote:
> On 11/6/07, skaller <[EMAIL PROTECTED]> wrote:
> > BTW: dirnames like build.svn aren't so hot, they confuse Windows.
> > Also, thinking of a tarball, the .svn is inappropriate anyhow.
>
> Oh, thats just my organizational scheme, I wouldn
On 11/6/07, skaller <[EMAIL PROTECTED]> wrote:
> BTW: dirnames like build.svn aren't so hot, they confuse Windows.
> Also, thinking of a tarball, the .svn is inappropriate anyhow.
Oh, thats just my organizational scheme, I wouldn't suggest anyone follow it :)
You could just replace "felix.svn" wi
On Mon, 2007-11-05 at 22:22 -0800, Erick Tryzelaar wrote:
> Say we do this:
>
> > mkdir felix.svn
> > svn co ... felix.svn
> > mkdir build.svn
> > cd build.svn
> > ../felix.svn/autogen.py
>
> So, going through your list, we've got:
>
> > A. source: not modified by build, edited by devel
Say we do this:
> mkdir felix.svn
> svn co ... felix.svn
> mkdir build.svn
> cd build.svn
> ../felix.svn/autogen.py
So, going through your list, we've got:
> A. source: not modified by build, edited by developers
that'd be felix.svn
> B. build: created and modified by build, mu
The Felix build model is changing as follows.
1. In place builds are no longer supported. It should work for
a while, but cleanup and dependency checking may fail. I do this
all the time so I'm going to have to unlearn this habit.
Instead, builds must be done in a separate directory isolated
from
