[Gd-hackers] Restructuring the repository

[Peter Robisch]

Hallo all,

 If we start a website restructuring, I think restructuring the
Subversion based repository is also a good idea.  

Subversion's main idea is to version configurations rather than atoms.
So only a configuration has a version number - not its parts.
Currently all Dylan stuff is in one Subversion repository. IMHO having
several repositories would reflect Subversion concept of configurations
in a better way. I list several possible repositories in the appendix
below.

Of course we will need therefore a Dylan wrap of Subversion C-libraries.
Such a Subversion lib-wrapping could be integrated in the jam-based
build process of OD, for example. As Housel is working on a melange
replacement called CPR (see http://www.opendylan.org/melange.phtml ).
>From my understanding with CPR we will have a general interacting with C
for both, the harlequin and the gwydion compiler. 

The proposed repository restructuring will IMHO allow to smoothly fusion

Gwydion and Harlequin code. 

Pet-ro 


APPENDIX 

As Subversion's main idea is to version configurations rather than
atoms, only a configuration has a version number - not its parts. We
propose here to use several Subversion repositories. 

The goal of the proposed repository restructuring is to support smooth
process of Merging Gwydion and Harlequin code.

Feel free to discuss and improved this draft.  
Feel free to turn this draft into a wiki topic called for example
"Repository Restructuring", if you feel this simplifies commenting on
this draft.


Turn the one Subversion into several repositories. A list of possible
repositories follows:

* compiler-gwydion                       
* compiler-harlequin
* compiler-common     
=> The compiler repositories contain only what's necessary 
   for command-line-based compiling.
   - compiler-common contains stuff that is usable by both compilers

* ide-harlequin                 
* ide-common
=> all the stuff that turns a command-lined-based compiler into an IDE
  (debug, interactor, code browser, etc.)
   - ide-common contains stuff that is usable by both compilers


* lib-common          all libraries that are checked (!)
                      to be compatible with both compilers
* lib-gwydion         all libraries depending on gwydion based APIs 
* lib-harlequin	    all libraries depending on harlequin based APIs
=> libraries which are not to focus on compiler or ide developing
   
* site-public    contains for example
      - pub-books      -- Dylan Reference Manual, Dylan Programming
      - pub-gwydion    -- gwydion specific manual, API documentations 
      - pub-harlequin  -- harlequin specific manual, API documentations

* site-internal
       - the website content (pages, wiki, etc),         

* archive-internal-gwydion     --- deprecated stuff related to Gwydion
* archive-internal-harlequin   --- deprecated stuff related to Harlequin

=> especially in the Fun-Dev folder and in the documentation folder 
   of the current repository there are several old documents 
   which relate to the design process and the coding environment 
   used at Harlequin. They are interesting, but not to the broad Open
Dylan
   community.
   As this folder might also contain for example scripts and C-code it
is
   call archive. Otherwise one might call it doc