[squeak-dev] Installer class side location methods and pbworks.com documentation

Tobias Pape Das.Linux at gmx.de
Mon Aug 26 08:33:41 UTC 2019


Hi tim
> On 23.08.2019, at 20:40, tim Rowledge <tim at rowledge.org> wrote:
> 
> 
> 
>> On 2019-08-23, at 10:20 AM, Tobias Pape <Das.Linux at gmx.de> wrote:
>> 
>> Hi tim
>> 
>>> lukas (seems to be very out of date?)
>> 
>> essentially frozen, but why would that be invalid?
>> If you want to try Lukas Renggli's stuff, that would be the go-to-location.
> 
> True, but is it still interesting enough to warrant a utility link in a system class? And it returns an empty list for 
> Installer lukas basicAvailablePackages 

That's because it isn t a single repository but a collection thereof, just like squeaksource.

If you want to look at his Functional Pattern Matching stuff,  do

	`(Installer lukas project: 'fpm') basicAvailablePackages`

> I'm not suggesting any of the repositories are junk (aside from the ones simply no longer there) but is they no longer respond to the utilities in the Installer classes then they probably shouldn't be listed therein.



> 
>> 
>>> saltypickle (no domain - but it is for sale!)
>>> sophie (no domain - also for sale - whee!)
>>> ssMirror (no server)
>>> swasource (seems to have a squeaksource3 service but nothing in it?)
>> 
>> It works if you know what to install.
>> I have removed the ss3 project listing and especially the authors listings, as I am unsure what is admissible under the European Privacy regulations. 
>> We use it at HPI primarily for our students' projects, so these must stay private.
> 
> That's fine, though unfortunate since there is likely intersting stuff.

yeah, but https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/ is a better staring point.

For most of the software you can't just take the monticello browser and start loading some packages, as there's typically more steps involved to get going.

> 
>> 
>> However, all the public stuff is still public, just not on the front page.
> 
> Finding a way to get it listed in response to a #basicAvailablePackages etc would be a bit help. How else are we supposed to find them?

Note that #basicAvailablePackages doesn't work for `Installer squeaksource` either.
It seems to be repository specific, not repository-collection-aware.
And how could it? We have no canonical way of denoting "this is  a collection of Monticello repositories" to a Squeak image.

Yes, HPI's SqueakSource repos are documented out-of-band (see the Squeak Community Project link above).
I have no intention to re-list stuff at the moment, because I have no time to think through the legal implications (we're in the EU, after all…) 

That said, please keep the shortcut :)

Best regards
	-Tobias

PS: you'll notice that some packages on the page, eg, https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/macros do not even use the shortcut. That's because they were worked on before I put the shortcut into trunk. 
We're making heavy use of the shortcut when preparing our biannual Squeak Images for students. :)


More information about the Squeak-dev mailing list