Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
Locked
Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
 
|
>
> did you check the configurationOfFFI ??? > Does it exist? > > Stef > > On Feb 14, 2010, at 7:45 AM, Yanni Chiu wrote: > >> Oops, this was on Pharo. I just checked Squeak3.11-9371-alpha.zip, and ScriptLoader>>loadFFI does not exist there. >> >> Anyhow, what is the proper way to load FFI? >> >> >> Yanni Chiu wrote: >>> "ScriptLoader loadFFI" now fails because the package FFI-Examples is no longer in the repository. >>> Does ScriptLoader need to be updated, or was the package deleted accidentally? >> >> > > > > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
|
|
Try not to use ScriptLoader anymore to load projects or packages.
To install FFI, use the Metacello configuration, like this: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. ((Smalltalk at: #ConfigurationOfFFI) project version: '1.0') load. Cheers Mariano On Sun, Feb 14, 2010 at 10:48 AM, Stéphane Ducasse <[hidden email]> wrote: > _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
|
|
In reply to this post by Stéphane Ducasse
The last word on Metacello, that I recall reading in this list, is that
it is an experiment. Has that changed? I'm happy enough to changed my habits, if that is the case. In this case, my build script was loading Albatross, which had the dependency on FFI (so I was not directly interested in FFI). The script I had was pieced together somehow, long ago, and was using #loadFFI, which worked fine until a few days ago. BTW, since all FFI-Examples packages were removed from the FFI repository, even Metacello "versions" would fail because the package is no longer there. -- Yanni Stéphane Ducasse wrote: >> did you check the configurationOfFFI ??? >> Does it exist? >> >> Stef >> >> On Feb 14, 2010, at 7:45 AM, Yanni Chiu wrote: >> >>> Oops, this was on Pharo. I just checked Squeak3.11-9371-alpha.zip, and ScriptLoader>>loadFFI does not exist there. >>> >>> Anyhow, what is the proper way to load FFI? >>> >>> >>> Yanni Chiu wrote: >>>> "ScriptLoader loadFFI" now fails because the package FFI-Examples is no longer in the repository. >>>> Does ScriptLoader need to be updated, or was the package deleted accidentally? _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
|
|
On Sun, Feb 14, 2010 at 10:09 PM, Yanni Chiu <[hidden email]> wrote: The last word on Metacello, that I recall reading in this list, is that Metacello seems to be very stable, not an experiment any more. There are a lot of big projects that are being managed with it such us Moose, GLASS, PharoDev images, etc. Take a look to http://www.squeaksource.com/MetacelloRepository for all the available configurations. Nevertheless, Metacello hasn't released the 1.0 stable version. It is still in beta state, but I think the 1.0 will be very soon.
Thank for the report. I have just commited a new version that fix this and another couple of things. Can you tell me if it works ok for you ? Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. ((Smalltalk at: #ConfigurationOfFFI) project version: '1.0') load. I have one failing test :( testUlongRange
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
|
|
On Sun, Feb 14, 2010 at 11:04 PM, Mariano Martinez Peck <[hidden email]> wrote:
Sorry, It is this: ((Smalltalk at: #ConfigurationOfFFI) project version: '1.2') load.
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
|
|
Mariano Martinez Peck wrote:
> Thank for the report. I have just commited a new version that fix > this and another couple of things. Can you tell me if it works ok > for you ? > > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfFFI'; > load. > > ((Smalltalk at: #ConfigurationOfFFI) project version: '1.0') load. > > > Sorry, It is this: > > ((Smalltalk at: #ConfigurationOfFFI) project version: '1.2') load. It works fine. Thanks. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
In reply to this post by Yanni Chiu
----- "Yanni Chiu" <[hidden email]> 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. As far as I am concerned, it is a cardinal sin to remove packages from a public repository, since folks may actually expect to use the older versions ... the repository owner can do their own thing of course and presumably have their reasons... We'll have to mark the earlier versions of FFI as broken in the Metacello config unless we can recover the older files... Dale _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
|
|
El mar, 16-02-2010 a las 13:25 -0800, Dale Henrichs escribió:
> ----- "Yanni Chiu" <[hidden email]> 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. > > As far as I am concerned, it is a cardinal sin to remove packages from a public repository, since folks may actually expect to use the older versions ... the repository owner can do their own thing of course and presumably have their reasons... > > We'll have to mark the earlier versions of FFI as broken in the Metacello config unless we can recover the older files... > Yes, good idea, some kind of pragma marker on a otherwise unmodified old version method in ConfigurationOfXXX will allow the tools to present the version but highlight their brokeness. cheers > Dale > > _______________________________________________ > Pharo-project mailing list > [hidden email] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel Cobá http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
In the current Metacello, you can set the blessing to #broken and the version will be ignored in certain calculations like latestVersion...
Dale ----- "Miguel Enrique Cobá Martinez" <[hidden email]> wrote: | El mar, 16-02-2010 a las 13:25 -0800, Dale Henrichs escribió: | > ----- "Yanni Chiu" <[hidden email]> 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. | > | > As far as I am concerned, it is a cardinal sin to remove packages | from a public repository, since folks may actually expect to use the | older versions ... the repository owner can do their own thing of | course and presumably have their reasons... | > | > We'll have to mark the earlier versions of FFI as broken in the | Metacello config unless we can recover the older files... | > | | Yes, good idea, some kind of pragma marker on a otherwise unmodified | old | version method in ConfigurationOfXXX will allow the tools to present | the | version but highlight their brokeness. | | cheers | > Dale | > | > _______________________________________________ | > Pharo-project mailing list | > [hidden email] | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | -- | Miguel Cobá | http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
|
|
In reply to this post by Dale
Dale Henrichs wrote:
> ----- "Yanni Chiu" <[hidden email]> 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 [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore
|
|
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: [hidden email] [mailto:[hidden email]] On Behalf Of Yanni Chiu Sent: Wednesday, February 17, 2010 12:00 AM To: [hidden email] Subject: Re: [Pharo-project] Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore Dale Henrichs wrote: > ----- "Yanni Chiu" <[hidden email]> 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 [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
|
|
In reply to this post by Yanni Chiu
----- "Yanni Chiu" <[hidden email]> wrote: | Dale Henrichs wrote: | > ----- "Yanni Chiu" <[hidden email]> 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. This was a comment about keeping Pharo-level repositories, rather than individual repositories. In theory the Metacello configuration is created by the maintainers of the project, so in theory the maintainers won't remove packages that are needed for development and won't remove packages for which they've published a version. In practice, the FFI configuration is maintained by Pharo and the code in question is being managed by Squeak (and the Squeak folks aren't using Metacello). If Pharo has it's own repository for things like FFI, etc. then the problem of disappearing packages shouldn't happen. | | > 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. There's no question that the folks managing that repository had a good reason for doing what they did, but if a developer happened to have branched FFI-Examples, she'd be SOL, unless she copied the packages in self defense...which is Lukas' point. If you are going to depend upon a set of packages in a repository, then you are at the mercy of the maintainers of the repository as far as uptime as well as contents. | | > 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). I assume that FFI is actually being maintained in separate (private) repository and the public repository (where we've been grabbing FFI) is simply a staging area for publishing the latest version of the code... Dale _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |