Cool. So far the only strange thing I see is with RPackage RPackages (:)). The RPackage package duplicates all extensions listed in RPackage-* packages. But this may be a problem with MC, not with RPackage in itself. I'll try a few extensions additions to check. Thierry ________________________________________ De : pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] de la part de Esteban Lorenzano [estebanlm@gmail.com] Date d'envoi : mardi 11 septembre 2012 17:26 Ã : Pharo-project@lists.gforge.inria.fr Objet : Re: [Pharo-project] [update 2.0] #20279 yes it is :) On Sep 11, 2012, at 5:14 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote:
Le 11/09/2012 16:18, Esteban Lorenzano a écrit :
20279 -----
Issue 6654: Make one RPackage maps one PackageInfo http://code.google.com/p/pharo/issues/detail?id=6654
(pass 1)
- Rollback Nautilus to a pre-tags version - initialize RPackageOrganizer from PackageInfos as before
WARNING: This does not restores 2.0 stability, but it makes it a bit more usable... I'm working on the other issues.
Works for me.
I see one RPackage for each system categories, not one RPackage per PackageInfo, and no RPackageSet yet.
Is that what we should expect?
Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95