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" <[email protected]> wrote: | El mar, 16-02-2010 a las 13:25 -0800, Dale Henrichs escribió: | > ----- "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. | > | > 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 | > [email protected] | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | -- | Miguel Cobá | http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
