And, it seems logical for the SM app to have an indicator to say that the Safe to Install filter is on, and provide a way to turn it off in case a programmer needs to find old code to test.

There's nothing to indicate what 'SqueakMap Package Loader (7 shown out of 773 packages)' means.

- Darius

On Wed, Dec 28, 2011 at 12:10 PM, Frank Shearar <frank.shearar@gmail.com> wrote:

On 28 December 2011 17:38, Darius Clarke <socinian@gmail.com> wrote:
>
> On Wed, Dec 28, 2011 at 9:16 AM, Darius Clarke <socinian@gmail.com> wrote:
>
>>
>> But a current SqueakMap refresh in 4.3 has almost none of the prior
>> applications in it any more. It's been neglected too by the community.
>
>
> Correction: With the "Safe To Install" filter turned on by default.

Given that 4.3 is 3 days old, isn't that to be expected? Quoting from
Swiki (http://wiki.squeak.org/squeak/2726),

"With Squeak 4.2, the SqueakMap Catalog opens without the rot showing.
Whenever a new version of Squeak is released, all of the packages that
were visible in the list in the prior version no longer appear in the
new version. This is because the SqueakMap process requires authors to
re-designate their applications as working in the new Squeak release."

Now one could have some kind of server sitting somewhere taking a
fresh image and running install scripts with some kind of script
verifying that the package loaded correctly (say, by running the
package's tests), and on a green light marking the SM package as "Safe
To Install". But at any rate, right now it's up to the package owner
to perform this task.

frank

> Darius
>
>
>