In the interest of keeping small changes, I would have thought it would be
very easy to do a renaming of the source level directory layout to as
proposed (I have no strong opinion on rel/ priv/ etc)
+ src
+ ebin
+ couch.app
+ lib
+ ejson
+ src
+ ibrowse
+ src
and keep the build toolchain exactly the same, this would make it easier for
people who want to start using tools that expect otp compliance, like rebar
/ reltool / agner etc (in erldocs I had to patch is specifically to support
couchdb's layout)
in future things like rebar could be supported / integrated, but a simple
source reorg seems like it wouldnt be too intrusive for a first step
Cheers
Dale
On 21 June 2011 16:30, Benoit Chesneau <[email protected]> wrote:
> On Tue, Jun 21, 2011 at 4:25 PM, Paul Davis <[email protected]>
> wrote:
> > On Tue, Jun 21, 2011 at 2:25 AM, Benoit Chesneau <[email protected]>
> wrote:
> >> Hi all,
> >>
> >> I'm back on this topic. I know that @davisp made a script to split the
> >> file structure etc, but I wonder why or what we are waiting to do
> >> this. Also why using a script when we could move everything once? (and
> >> it should be done once imo)
> >>
> >
> > As to why that never hit trunk, its because there weren't enough
> > people testing it to make me feel comfortable pushing it in. And then
> > I got distracted by other things. The reason this must be a script is
> > that SVN doesn't track history based on diffs. If we did this in Git
> > and then tried to push that series of patches to SVN, it'd result in
> > removing the history for every source file in SVN. And instead of
> > going Rambo style and doing it against trunk, I wanted to be able to
> > test it and let others test it.
> >
>
> Wasn't suggesting it was your fault :) Lack of feedback is always annoying.
>
> I think we can go chunk by chunk in a branch and merge everything at
> the end and keep the same advantage. That's actually how I do it. I'm
> not sure I like to use script for that, this is something where I
> would like to have my hands dirty.
>
> - benoƮt
>
> - benoit
>