I agree that there is a contradiction between being self-sufficient and enjoying the benefits of central repositories. I have already encountered show-stoppers for Windows installation of Rio (Linux to the rescue) and was forced to create a local-only mode in my current loader. It is one thing to be hobbled by a temporary outage of a free service, but it is quite another to be vulnerable to deletions such as described below.
One option would be for the files to go in but not come out w/o some effort, or perhaps for files to be uploaded in (hopefully) consistent groups that the owner can delete as an all-or-nothing set?? Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Yanni Chiu Sent: Wednesday, February 17, 2010 12:00 AM To: [email protected] Subject: Re: [Pharo-project] Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore Dale Henrichs wrote: > ----- "Yanni Chiu" <[email protected]> wrote: > > | BTW, since all FFI-Examples packages were removed from the FFI > | repository, even Metacello "versions" would fail because the package > | is no longer there. > > This underscores Lukas' argument that you need to create your own repository > of packages that you use. I don't understand how this jives with Metacello. If I depend on a Metacello configuration then I inherit the repository dependencies of that configuration -- unless I maintain my own copy of the configuration and the packages it references. > As far as I am concerned, it is a cardinal sin to remove packages from a > public repository ... I agree. I assume the reason for removing the package was to eliminate confusion caused when the latest version of the package is loaded, but doesn't work, because none of the code should be there. Another approach might have been to delete all the classes/methods from the package, and submit it as the latest version. Though I'm not sure Monticello would accept an "empty" package. > We'll have to mark the earlier versions of FFI as broken in the Metacello > config unless we can recover the older files... I probably can find an old version in a package-cache, but the repository for FFI is on http://source.squeakfoundation.org, which seems to be the active code base for Squeak (correct me if I'm wrong). -- Yanni _______________________________________________ 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
