Re: Re: Progress

[2003-07-22] David Abrahams wrote:

>Rene Rivera <[email protected]> writes:
>
>> [2003-07-22] Daniel Wallin wrote:
>>
>>>Can we try to move this along? I'm still waiting for your follow up on
the
>>>registries thread Dave.
>>>
>>>Anyway, I have very little to do right now, so it  would be great if we
>>>could decide how these things should work so I can start migrating the
>>>luabind code to use the shared langbinding code.
>>
>> Perhaps we can start on setting up cvs for the changes while Dave gets
back
>> to the thread. [ I envy you on having free time ;-) ]
>>
>> 1. The branch... "langbinding" seems most logical as the branch. If there
>> are no objections I can add it pronto.
>
>Fine.  Please, though, don't branch all the directories.  Let's start
>by just branching the langbinding and python directories (and
>luabind, if you add that one).
>
>> 2. File organization. Current organization for Boost.Python is:
>>
>>     boost-root/boost/python/ [converter, detail, object]
>>     boost-root/libs/python/ [build, doc, example, src]
>>
>> I see three options for possible structure of the three parts of this.
First
>> a total split in the parts as libraries:
>>
>>     boost-root/boost/langbinding/...
>>     boost-root/libs/langbinding/...
>>     boost-root/boost/python/...
>>     boost-root/libs/python/...
>>     boost-root/boost/luabind/...
>>     boost-root/libs/luabind/...
>
><snip>
>
>> The first one seems the clearest to me. Thoughts?
>
>I agree with that.  At least the files users touch should be in
><boost/python>, <boost/luabind>, etc.

OK branch created and the following dirs created:

    /boost/boost/langbinding
    /boost/boost/luabind
    /boost/libs/langbinding
    /boost/libs/langbinding/build
    /boost/libs/langbinding/doc
    /boost/libs/langbinding/example
    /boost/libs/langbinding/src
    /boost/libs/langbinding/test
    /boost/libs/luabind
    /boost/libs/luabind/build
    /boost/libs/luabind/doc
    /boost/libs/luabind/example
    /boost/libs/luabind/src
    /boost/libs/luabind/test

Those dirs have either an "empty.txt" or some other appropriate placeholder
file in them. <sarcasm>Seeing as CVS handles directories with such
grace.</sarcasm>

Also /boost/python and /boost/libs/python are branched.

Some CVS instructions:

1. To get the dirs in the command line do:

    cvs co -r langbinding boost/boost/python

    or in wincvs:
    
    Remote:Checkout module...
    put in the "Module name..."
    select the "Checkout options" tab
    check the "By revision/tag/branch:" and put in langbinding
    press OK.

Repeat for the 6 directories.

2. When adding new files make sure to add them to the branch. This should be
automatic because the directories will be tagged with the branch but just in
case... After doing the "cvs add", in the command line the commit should be:

    cvs commit -m "comment" -r lanbinding [_file_or_dir_]
    
    or in wincvs:
    
    Modify::Commit...
    select "Commit options" tab
    check the "Force revision/branch" and put in langbinding
    press OK.


Daniel, or anybody else, if you have more CVS questions just ask :-)


-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0