On Mon, Apr 5, 2010 at 3:27 PM, Alexandre Bergel <[email protected]>wrote:
> 1) There are packages that should NOT be part of the core, but they are not >> also dev tools. For example, ObjectTracer, ObjectViewer, Morph examples, >> Sound, ImageSegment (?) etc. So...where do we put them ? >> > > I would imagine to have each package in a dedicated SqueakSource > repository, pretty much the same way we have OB, RB, NewInspector. > Yes, actually, the repository was alrady created in SqueakSource under the name of PharoNonCorePackages. > From what you wrote, I understand that you wish to create an intermediary > layer, PharoNonCorePackages > In that case: > Pharo = PharoVeryCore + PharoNonCorePackages + PharoDev > Is this what you intend ? Exactly. > Ideally, I do not see a valid reason for PharoNonCorePackages to be: each > package can happily live in its own SS rep. Yes, they can also live in their own repository. But I think it is easier to have the all together in the same repository. Mostly because I don't think there will be too much packages for the same repository. I mean, all those packages are little and seem not to be very related to each other...so it is not like a big project where you need a repository because you have a lot of packages for the same project. In this case we will probably have one package. > Moreover, this could easily create confusion. Why ? What is the difference with the Pharo repository for example ? > But for practical reason, it could make your life easier. > > yes! > Cheers, > Alexandre > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
