<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;"><div>"<br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">As you can imagine, filetree is one of the first github projects (using</span><br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">filetree):) and I made the platform per branch decision fairly early on</span><br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">and learned over time that it is not quite the right model to use ...</span><br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">and now it would be difficult to try to switch to a better model - </span><br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">branch per release with conditional platform code, is my current favorite..."</span><br></div><div><br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">If "branch per release with conditional platform code.." is the model for the Seaside compat, shouldn't we bite the bullet and make Filetree the same?</span><br></div><div><br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">If <span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">"branch per release with conditional platform code.." is NOT the model for the Seaside compat, somebody please inform me. </span></span><br></div><div><br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;"><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">thx.</span></span><br></div><div><br></div><div><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;"><span style="color: rgb(0, 0, 0); font-family: Lato; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;"></span></span><br></div><br><div data-zbluepencil-ignore="true" style="" class="zmail_extra"><br><div id="Zm-_Id_-Sgn1">---- On Tue, 11 Aug 2020 12:08:38 -0400 <b>Dale Henrichs <dale.henrichs@gemtalksystems.com></b> wrote ----<br></div><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); padding-left: 6px; margin: 0px 0px 0px 5px;"><div>Tim,<br><br>There is no master branch for filetree, the filetree project uses an <br>branch per platform model, I started out trying to keep the common code <br>on the master branch, but it proved to be too difficult, So each <br>platform is pretty much independent ... If it would help, I've invited <br>you to be a contributor to the filetree project so that you can do your <br>own management of the squeak support.<br><br>As you can imagine, filetree is one of the first github projects (using <br>filetree):) and I made the platform per branch decision fairly early on <br>and learned over time that it is not quite the right model to use ... <br>and now it would be difficult to try to switch to a better model - <br>branch per release with conditional platform code, is my current favorite...<br><br>I did see your issues, but I've been busy with working on some bugfixes <br>aimed at an imminent release and haven't had the time to look at it in <br>more detail ... things will be a little hectic for me over the next week <br>or so, but hopefully will settle down for a bit, before the next wave hits:)<br><br>Dale<br><br>On 8/11/20 8:20 AM, Tim Johnson wrote:<br>> It was working for me as of this weekend also.<br>><br>> If Timothy feels inspired, I could definitely use the help figuring <br>> out how to update the ConfigurationOfFileTree to use the 2016 commits <br>> from @krono as described in my recent post to the list.<br>><br>> Without this 2016 fix, the Grease repo doesn't load in Squeak's <br>> Monticello Browser, so efforts to work on the Seaside compatibility <br>> with Squeak (a.k.a., Grease) likely won't be fruitful.<br>><br>> I view this operation as rather complex, so could definitely use <br>> advice. I don't know if it's a question of asking Dale to cherry-pick <br>> these commits into the 'master' branch, or update the spec for Squeak, <br>> or both, or neither. It's also possible (*but unlikely*) that all of <br>> this has been done in /one/ repo, but that the 'Installer <br>> ensureRecentMetacello' is using some /other/ repo somewhere which <br>> contains an older spec or baseline missing these 2016 updates.<br>><br>> Thanks,<br>> Another Tim<br>><br>><br>> On 2020-08-10 12:09, Jakob Reschke wrote:<br>>> Forwarding missing posts to the list with Timothy's approval.<br>>><br>>> ---------- Forwarded message ---------<br>>> Von: gettimothy <<a href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>><br>>> Date: Sa., 8. Aug. 2020 um 19:48 Uhr<br>>> Subject: Re: [squeak-dev] Squeak6.0 alpha, install, add additional<br>>> stuff--Metacello, Git, OSProcess, Grift, Malfeascance, etc fails due<br>>> to smaltalkhub be bye-bye<br>>> To: Jakob Reschke <<a href="mailto:forums.jakob@resfarm.de" target="_blank">forums.jakob@resfarm.de</a>><br>>><br>>><br>>> With Smalltalkhub back up, everthing is installing nicely.<br>>><br>>> I can now focus on the Seaside compat between Squeak and Pharo.<br>>><br>>> However, my concerns still hold, it is a bit wierd that a script on<br>>> Gemstones depends on a script on SmalltalkHub.<br>>><br>>><br>>> cheers!<br>>><br>>> tty<br>>><br>>><br>>> ---- On Sun, 02 Aug 2020 16:12:54 -0400 Jakob Reschke<br>>> <<a href="mailto:forums.jakob@resfarm.de" target="_blank">forums.jakob@resfarm.de</a>> wrote ----<br>>><br>>> Probably related thread:<br>>> <a href="http://forum.world.st/Metacello-bootstrap-fails-due-to-download-timeouts-td5119637.html" target="_blank">http://forum.world.st/Metacello-bootstrap-fails-due-to-download-timeouts-td5119637.html</a> <br>>><br>>><br>>> Am So., 2. Aug. 2020 um 11:42 Uhr schrieb gettimothy via Squeak-dev<br>>> <<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.squeakfoundation.org</a>>:<br>>>><br>>>> Hi folks,<br>>>><br>>>> This probably holds for 5.3 install too.<br>>>><br>>>> In the preferences wizard, the extras stuff, the Install Metacello <br>>>> ... hangs at "Updating <a href="http://smalltalkhub.com/foo/bar/metacello/main" target="_blank">http://smalltalkhub.com/foo/bar/metacello/main</a>"<br>>>><br>>>> iirc, from the pharo discord, SmalltalkHub is going away.<br>>>><br>>>> You will probably need a different repo.<br>>>><br>>>> cordially,<br>>>><br>>>> tty<br>>>><br>>>><br>><br><br></div></blockquote></div><div><br></div></div><br></body></html>