[bind10-dev] layout of build system

[JINMEI Tatuya / 神明達哉]

Now I'm ready to start adding code to the main trunk and revisiting
the repository layout issue...

At Fri, 2 Oct 2009 08:14:25 -0500 (CDT),
"Jeremy C. Reed" <jreed at isc.org> wrote:
> 
> As discussed on call yesterday, we "need to decide on layout of build 
> system, headers go here, libraries go there, and so on"
> 
> Here is an idea. If this is an extracted tarball, it would be liked 
> bind10-A.B.C (version) instead of "bind10".
> 
> Note this doesn't distinguish or categories by languages used.
> 
> bind10/ 
> bind10/doc/
> bind10/src/
> bind10/src/doc/
> bind10/src/lib/
>         source for libraries
>         Makefile.am
>         documentation and design decisions
>         source for manual pages
>         all kept in sub-directories per specific libraries, such as:
> bind10/src/lib/dnsmessage

Evan showed his preference of omitting "src".  Is that our decision?
(I don't have a preference on this).

"dnsmessage" sounds a bit too specific, considering what will
eventually be included there.  Maybe a bit too generic, but I guess
"lib/dns" would be better, just like BIND9.

Another minor question is whether I begin with a branch or on the main
trunk for the moment.  I don't see a need for creating a branch while
keeping the main trunk almost empty, so I'll probably work directly on
the main trunk until branching is really necessary.

So, what I'm going to do is:

- create new directories on the main trunk:
  ${top}/
  ${top}/lib
  ${top}/lib/dns/
  (where ${top} is either bind10 or bin10/src depending on whether to
  include "src")
- add DNS message library code to ${top}/lib/dns/
- not sure where test code goes, but in my vague memory we slightly
  prefer the same directory as the source dir.  So I'll also add test
  code under ${top}/lib/dns/

If I misunderstand something fundamental please point it out.
Otherwise I'll soon invade the trunk.

---
JINMEI, Tatuya