diff options
author | Alan Coopersmith <alan.coopersmith@oracle.com> | 2013-09-14 15:27:00 -0700 |
---|---|---|
committer | Alan Coopersmith <alan.coopersmith@oracle.com> | 2013-09-14 15:27:00 -0700 |
commit | 380c2cbb85181801a8d07592c56718b4f0a075c9 (patch) | |
tree | d8e9760927fff610fde0a34bada1349a767e2359 /ModularizationProposal.mdwn | |
parent | f1f47b9cfb1eb36296830ee0213046d004356485 (diff) |
Restore modularization proposal images (thanks to archive.org!)
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Diffstat (limited to 'ModularizationProposal.mdwn')
-rw-r--r-- | ModularizationProposal.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/ModularizationProposal.mdwn b/ModularizationProposal.mdwn index b169f9e7..56021b6c 100644 --- a/ModularizationProposal.mdwn +++ b/ModularizationProposal.mdwn @@ -104,7 +104,7 @@ It is important to note that the modular source tree is expected to contain the The monolithic source tree will continue to exist as a self-contained source tree that can be built with imake, but it is expected that people will transition to the modular tree for future development (see the next section). We propose that both trees should co-exist side-by-side in the xorg CVS project hosted on freedesktop.org (see Figure 1 below). -[[!img http://www.freedesktop.org/~kem/modular/figure1.gif]] +[[!img figure1.gif]] From the Figure above, the monolithic source tree will continue in the `xc` hierarchy within the xorg project. Along side of it will be several separate modules: **app**, **lib**, **proto**, **xserver**, **driver**, **font**, **doc**, and **util**. Each of these modules will be detailed below. Not shown in Figure 1 are the _extras_, which will exist outside of the source tree and contain only those source tarballs required to build the tree, but for which xorg is not the canonical source repository. @@ -179,7 +179,7 @@ The _extras_: Now that we've seen what the modular source tree could look like in the section above, we can explain how to transition from our current monolithic tree to the proposed modular one. The transition can begin once this proposal has been finalized and accepted. Figure 2 shows the outline of how this transition will happen. -[[!img http://www.freedesktop.org/~kem/modular/figure2.gif]] +[[!img figure2.gif]] The modularization effort will begin by creating the top level modules. The order in which to create them is implicit in their dependencies (see previous section). During this development period, our goal is to share source files between both the monolithic and modular trees. |