Installer class side location methods and pbworks.com documentation

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Installer class side location methods and pbworks.com documentation

Michael Rueger

> Any chance the packages could just be uploaded to squeaksource.com? Likely not much would still load but there may be parts rescuable.

Yes, I think there could be some useful stuff there. But then I'm not exactly objective ;-)

I'll see when I find some time, hopefully soon. First need to dig through my archives

Cheers

Michael

Reply | Threaded
Open this post in threaded view
|

Re: Installer class side location methods and pbworks.com documentation

timrowledge
In reply to this post by keithy
That's pretty clever, and it's kind of sad that it can't work right now.

I found a few more bugs that could be fixed quite simply and might result in something that would enable much the same capability. I guess it can't be in regular use though or we'd hear complaints about the missing methods.

So aside from the wierdness about Installer web returning the InstallerWeb class etc, and the missing #scripts method, I see that the methods that help with parsing a web page to fid the  embedded script(s) got changed such that the pbwiki doc recipes are unusable - the tag is described as <code st=""></code> whereas the code specifies <code st></code st>. Unless anyone has a good technical reason to change the code here I'll leave it and just describe it that way in the comments.

Given that it doesn't work, doesn't seem to have any current use and we don't know what #scripts should do, I propose to remove the Installer class>>install: method. An equivalent capability ought to be in InstallerWeb anyway, if someone wants to reinvigorate it.

> On 2019-08-27, at 2:38 AM, Keith <[hidden email]> wrote:
>
> Hi Tim,
>
> I wrote it and I don't remember sufficient detail.
>
> The idea was part of a suite of capabilities for the Squeak4.1 "new development model".
>
> The capability was that each version of squeak would be created by applying a crafted script to the previous version, rather than hacking away at a trunk repo.
>
> The scripts for various targets could be tested out and edited by contributors as it was embedded in a wiki page. Bug fixes were supplied by mantis, and called up by fix numbers, and the code was found embedded in mantis pages.
>
> These scripts would also unload as many palaces from the main image as possible, moving them into a curated list of packages (Sake/Packages).
>
> Bob the Builder, a continuous integration and testing tool also built on Sake, would run the scripts, build and test the images, periodically or whenever anything changed.
>
> Keith
>
>
>
>
>
>


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
"Bother" said Pooh, when Piglet stubbed his fag out on the semtex.



Reply | Threaded
Open this post in threaded view
|

Re: Installer class side location methods and pbworks.com documentation

Michael Rueger
In reply to this post by Michael Rueger

had a brief look at the Sophie stuff, had forgotten that it is BSD license, not MIT.
So will probably take a bit more effort to sort things into Sophie and contributed buckets...


On 27/08/19 10:37 PM, Michael Rueger wrote:

>
>> Any chance the packages could just be uploaded to squeaksource.com? Likely not much would still load but there may be
>> parts rescuable.
>
> Yes, I think there could be some useful stuff there. But then I'm not exactly objective ;-)
>
> I'll see when I find some time, hopefully soon. First need to dig through my archives
>
> Cheers
>
> Michael
>

12