Comment #8 on issue 3609 by cy.delau...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
RPackage tests and Monticello tests should be green in a 1.3 core image
with that:
load rpackage
Gofer new
squeaksource: 'PharoTaskForces';
Comment #9 on issue 3609 by fernando...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
Added the convienience method
SimplePackageOrganizerBrowseropenOnGlobalPackages.
Because the class comments were lacking a working example. If agreed, then
we could
Comment #4 on issue 3609 by cy.delau...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
Ok, it should work now with that:
load rpackage
Gofer new
squeaksource: 'PharoTaskForces';
package: 'ConfigurationOfRPackage';
Comment #5 on issue 3609 by cy.delau...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
Finally I does not have the rigth to edit the file rpackage.st.
Comment #6 on issue 3609 by marcus.d...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
fixed the permissions
Comment #7 on issue 3609 by cy.delau...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
load rpackage
Gofer new
squeaksource: 'PharoTaskForces';
package: 'ConfigurationOfRPackage';
load.
(Smalltalk globals at:
Comment #3 on issue 3609 by marcus.d...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
Hi,
I made a Hudson for RPackage (loading it in the latest 1.3)
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20RPackage/
load fails,
Status: Accepted
Owner: cy.delau...@gmail.com
New issue 3609 by cy.delau...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
RPackage aims to replace PackageInfo with a faster and cleaner
implementation.
What RPackage is already able to do (or at least
Comment #1 on issue 3609 by cy.delau...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
Another point to look at:
Monticello needs to know what are the sub-categories of a package before
saving it to a repository.
That work was concretly done by
Comment #2 on issue 3609 by tudor.gi...@gmail.com: Integrate RPackage
http://code.google.com/p/pharo/issues/detail?id=3609
The decision in RPackage is to match categories 1-to-1 to packages. Thus,
an RPackage will not have subcategories.
10 matches
Mail list logo