Re: [Bugs-r-devel] BUGS-R

[Gregor G. <gre...@bf...>]

Uwe Ligges wrote:
> Gregor Gorjanc wrote:
>> Uwe hello!
>>
>> I have just imported R2WinBUGS and BRugs package to SVN at BUGS-R.
>> Please subscribe to the bugs-r-devel list. 
> 
> I just did so.

Great

>> I have a question about
>> OpenBUGS folder in BRugs package. I have not yet added this one as I am
>> wondering if it is wise to have this as a subfolder in SVN. OpenBUGS is
>> a project by itself. Am I right that this is exact copy of OpenBUGS from
>> Finland servers? I am not sure we should put OpenBUGS into inst folder.
> 
> See below.
> 
>> Hmm, I totally agree that having OpenBUGS in BRugs package eases the
>> installation and that is great! I just wonder if we could hook something
>> like:
>>
>> - We have BUGS-R SF project with its SVN
>> - Perhaps (I hope so) there will also BUGS SF project with SVN
> 
> I doubt. It's Andrew Thomas. He is quite a clever guy, but he won't use
> such a tool. You cannot believe how his

I see. Perhaps we could "persuade" him somehow to start using these
tools. It seems that this will not be an easy job. But I think that such
tools provide a nice way to monitor the progress and learn the code by
doing this. This seems to be essential for BUGS as it is written in
unpopular/unknown language. I will mail Andrew and we can see if I can
offer any help here to make this idea alive.

>> - Then developer could have the following structure
>>
>> bugs-r/BRugs
>> bugs-r/BRugs/R
>> ...
>> bugs-r/BRugs/inst
>> ...
>>
>> from BUGS-R SVN and
>>
>> in bugs-r/BRugs/inst also
>>
>> bugs-r/BRugs/OpenBUGS
>>
>> from BUGS SVN. This of course relies on assumption that OpenBUGS in
>> BRugs package is exact copy of OpenBUGS. We could also take care of
>> versions via trunk/branches folders.
>>
>> Can we please discuss this issue?
>>
>> P.S. Nobody (except you!) sent me yet SF usernames ;(
> 
> That's what I assumed before.

To bad. I will also inform other from previous SF&BUGS discussions about
BUGS-R. Hopefully, BUGS-R will get more attention.

> Re. integration of OpenBUGS:
> It is most of the times the official version, but it also has been a
> fixed version that was not available on the BUGS site two times already.

Additional reason for having BUGS in SVN like system, but you already
know that.

> I think we should assume the recent OpenBUGS version for development and
> include some text file into the inst directory that explains what to do
> for the release cycle (i.e. copying OpenBUGS into the package).

What exactly are you proposing here:

A To import current OpenBUGS tree into SVN (in BRugs/inst/) and then
update it now and then.

B Just copy OpenBUGS in inst map and publish complete BRugs package on
CRAN. Text file would indicate this process.

I am more in favour to option B. This way we can still hope for
BUGS-core SF project to become alive.

Gregor