Re: About RPackage
Posted by
Stéphane Ducasse on
Mar 02, 2011; 8:09am
URL: https://forum.world.st/About-RPackage-tp3330650p3331134.html
On Mar 1, 2011, at 10:57 PM, Tudor Girba wrote:
> Hi Stef,
>
> This was the decisions that two of us (I mean me and you) took :).
Yes I remember :)
> Categories are mapped one-to-one to RPackages. The reason is that this is the simplest path to replace categories in the system.
>
> The second step is to map the current Monticello package to RPackages so that we can load existing Monticello packages.
a path is probably to evaluate the current categories and merged/reorganize them to look like packages.
Of course some people will cry but this is the way to go.
> The third step is to provide saving only of individual RPackages. Thus, Monticello should not save multiple RPackages into one Monticello package, but only make it easy to store each one in a separate package.
>
> Once this is achieved, we can merge an RPackage with a Monticello package, which means that the package that you see in the image is directly storable in a transparent way.
yes
>
> Cheers,
> Doru
>
>
>
> On 1 Mar 2011, at 22:44, Stéphane Ducasse wrote:
>
>> Hi cyrille/doru and others.
>>
>> I do not understand why
>> RPackage organizer packages contains System?
>>
>> In fact all the categories are mapped to packages and I wonder why.
>> I imagine that this is to avoid to have mostSpecific* logic of packageInfo,
>> but it means that in such a case we should merge categories to get back the package we have right now
>> else we will end up with loading/saving problems.
>>
>>
>> Stef
>
> --
> www.tudorgirba.com
>
> "Presenting is storytelling."
>
>