May 2024 - Pharo-dev - lists.pharo.org

This week (22/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 12 - Backport use of icon #smallPharo in #pharoItemsOn: for WorldState and #menuCommandOn: for ProfStef #16695 https://github.com/pharo-project/pharo/pull/16695 # Fixes - fix Reflectivity API #link:toAST: for metaclasses to fix debug points on class-side methods #16701 https://github.com/pharo-project/pharo/pull/16701 - Pharo13 fficalls athens cairo surface #16679 https://github.com/pharo-project/pharo/pull/16679 - Fix a small bug with FFI calls when passing 'NULL' as argument to the C function #16562 https://github.com/pharo-project/pharo/pull/16562 - eflectivity fixing bytecode to ast mapping #16489 https://github.com/pharo-project/pharo/pull/16489 # Improvements - Add libgit 1.8 support for Pharo 13 #86 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/86 - It should be possible to reset a ZnCharacterReadStream #16707 https://github.com/pharo-project/pharo/pull/16707 - Make #withCloseBox and #withPinBox on MenuTitleMorph use a FormSet for the button label #16696 https://github.com/pharo-project/pharo/pull/16696 - fix #needRequestorScope of StDebuggerContextInteractionModel so that its bindings can be used when evaluating code in the debugger #762 https://github.com/pharo-spec/NewTools/pull/762 - Adopt to new spec #761 https://github.com/pharo-spec/NewTools/pull/761 - Adding entry completion setter to SpRequestDialog #1540 https://github.com/pharo-spec/Spec/pull/1540 # Cleanups - Cleanup TraitTest>>#testRemovingTraitsRemoveTraitedClassMethodsWithSubclasses #16717 https://github.com/pharo-project/pharo/pull/16717 - Cleanup ReOverridingExtentsionMethod>>#basicCheck: #16715 https://github.com/pharo-project/pharo/pull/16715 - Fix lint issue on ZnEncodedStream #16713 https://github.com/pharo-project/pharo/pull/16713 - Fix lint issues on ZnEncodedReadStream #16711 https://github.com/pharo-project/pharo/pull/16711 - Cleanup: ZnCharacterEncoder, ZnEncodedStream, ZnEncodedReadStream and ZnEncodedWriteStream should be abstract classes #16709 https://github.com/pharo-project/pharo/pull/16709

May 31, 2024

This week (21/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 11 backports - P11 - During compilation there are redundant allocation of collections #16485 https://github.com/pharo-project/pharo/pull/16485 # Pharo 12 - Fix for pharo/pharo-project#16677: libgit2 library not listed in LGitLibrary>>#unix64LibraryName #85 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/85 # Fixes - 15652-Check-and-add-test-for--CompiledCodenewFrom #16663 https://github.com/pharo-project/pharo/pull/16663 - Debug points cleaning fixing #16670 https://github.com/pharo-project/pharo/pull/16670 - Change #pharoItemsOn: for WorldState and #menuCommandOn: for ProfStef to use the icon #smallPharo #16496 https://github.com/pharo-project/pharo/pull/16496 # Scriptable Debugger - Migrate to Tonel V3 #97 https://github.com/pharo-spec/ScriptableDebugger/pull/97 - Cleanup: do not use #notNil, use #isNotNil instead #96 https://github.com/pharo-spec/ScriptableDebugger/pull/96 # Rules / Refactoring Engine - Make class abstract driver #16347 https://github.com/pharo-project/pharo/pull/16347 - proposition for a potential new rule: use deny: instead of assert:equals:false #16668 https://github.com/pharo-project/pharo/pull/16668 # Cleanup - Debug point refactoring #757 https://github.com/pharo-spec/NewTools/pull/757 - Remove empty Manifests from baseline packages, synchronize on the tagâ¦ #16537 https://github.com/pharo-project/pharo/pull/16537 - Remove VariableLayout from tests #16686 https://github.com/pharo-project/pharo/pull/16686 - 16680-Zinc-uses-old-Announcers-API #16681 https://github.com/pharo-project/pharo/pull/16681 - 16608 cleanup crown initialize should call super initialize #16676 https://github.com/pharo-project/pharo/pull/16676 - Deprecate RPackageSet #16675 https://github.com/pharo-project/pharo/pull/16675 - Update call to a deprecated class #16671 https://github.com/pharo-project/pharo/pull/16671 - fixes #16610: Cleanup: simple typo in Crown class comment #16666 https://github.com/pharo-project/pharo/pull/16666

May 24, 2024

Re: Info required for bootstrapping pharo on GNU Guix

by Tim Mackinnon

While it sounds like a lot of work - if thats your itch I suppose its a good test of the work that Stephane mentions. By redoing it in a different environment it might iron out any accidental environment dependencies. Presumably its just the VM you need to bootstrap - as I would view the image as being like a Word or PDF document - and would be surprised that they would expect you to bootstrap those too? Good luck - and courage. Tim On Tue, 21 May 2024, at 9:47 AM, Nicolas Graves via Pharo-dev wrote: > On 2024-05-21 09:34, stephane ducasse wrote: > >> Hi >> >> Why canât you use the latest Pharo vm and Pharo12? >> We worked like mad over the years to get a much better system. >> Now why do you need to bootstrap Pharo because you can just use a bootstrapped image >> and get pharo working and running? > > Guix is not using the FHS filesystem so it would be a mess to try and > bootstrap from binaries. On top of that, they focus on > reproducibility. The standard on this end is to try and not use any > binary code if it's possible to build if from source, and yes, it > requires working like mad over the years. The website is currently down, > but there's an article about how they get all 30k packages from only a > single tiny binary file. > > Some of the guys behind Guix are also involved in bootstrappable.org > > I understand and share that the current system is much better, it's just > that to comply with their standard, that's what I have to do. > > What I understand from there it that it's feasible: > https://x.com/estebanlm/status/1042719107307712514 > > I'll do the work if feasible, I just can't find the information where I > should start from, hence my email. > > Best, > Nicolas > >> >> S >> >>> On 21 May 2024, at 09:31, Nicolas Graves via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >>> >>> Hi Pharo community, >>> >>> I'm trying to package pharo in the GNU Guix linux distribution. Since >>> the distribution is focused on reproducibility and avoids using binary >>> code when possible, for that I need to reproduce the bootstrapping steps >>> that are embedded in Pharo. I understand from some developper online >>> comment that this is possible. >>> >>> I've started to work on this and it seems feasible, at least I get the >>> dependency loop, what I've some difficulty is to get precisely when it's >>> possible to get started. >>> >>> ------------------- >>> | v >>> pharo VM pharo >>> â§ | >>> ------------------- >>> >>> If I'm correct, >>> - bootstrapping is very clear after version ~7.0.0, and with a proper >>> build, just follow the distribution numbers in wget's with a cmake >>> build-system. >>> - for earlier versions, there's the repository >>> https://github.com/pharo-project/PharoBootstrap >>> that seems (git history) to be able to go back to Pharo 30. >>> - I understand that at some point, Squeak and Pharo used to have the >>> same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen >>> this is in Pharo's ftp files, so I guess I can start there. >>> >>> What I need: >>> - Some indication about the first version of Pharo that I'm able to >>> build purely from squeak-vm, and where to find its source code >>> (git+version or commit if possible, I seem to only be able to find its >>> binaries currently in phero's ftp files). >>> - Any useful information for early bootstrap steps. >>> >>> Some useful information on my side: >>> - During the build process in Guix, we can't download data, so the >>> entire bootstrap chain has to be explicited at once, hence the need to >>> go back to the beginning in this case. >>> >>> Thanks in advance! >>> >>> -- >>> Best regards, >>> Nicolas Graves >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> 06 30 93 66 73 >> >> "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes >> >> >> >> >> > > -- > Best regards, > Nicolas Graves

May 21, 2024

Re: Info required for bootstrapping pharo on GNU Guix

by Nicolas Graves

On 2024-05-21 09:34, stephane ducasse wrote: > Hi > > Why canât you use the latest Pharo vm and Pharo12? > We worked like mad over the years to get a much better system. > Now why do you need to bootstrap Pharo because you can just use a bootstrapped image > and get pharo working and running? Guix is not using the FHS filesystem so it would be a mess to try and bootstrap from binaries. On top of that, they focus on reproducibility. The standard on this end is to try and not use any binary code if it's possible to build if from source, and yes, it requires working like mad over the years. The website is currently down, but there's an article about how they get all 30k packages from only a single tiny binary file. Some of the guys behind Guix are also involved in bootstrappable.org I understand and share that the current system is much better, it's just that to comply with their standard, that's what I have to do. What I understand from there it that it's feasible: https://x.com/estebanlm/status/1042719107307712514 I'll do the work if feasible, I just can't find the information where I should start from, hence my email. Best, Nicolas > > S > >> On 21 May 2024, at 09:31, Nicolas Graves via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >> >> Hi Pharo community, >> >> I'm trying to package pharo in the GNU Guix linux distribution. Since >> the distribution is focused on reproducibility and avoids using binary >> code when possible, for that I need to reproduce the bootstrapping steps >> that are embedded in Pharo. I understand from some developper online >> comment that this is possible. >> >> I've started to work on this and it seems feasible, at least I get the >> dependency loop, what I've some difficulty is to get precisely when it's >> possible to get started. >> >> ------------------- >> | v >> pharo VM pharo >> â§ | >> ------------------- >> >> If I'm correct, >> - bootstrapping is very clear after version ~7.0.0, and with a proper >> build, just follow the distribution numbers in wget's with a cmake >> build-system. >> - for earlier versions, there's the repository >> https://github.com/pharo-project/PharoBootstrap >> that seems (git history) to be able to go back to Pharo 30. >> - I understand that at some point, Squeak and Pharo used to have the >> same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen >> this is in Pharo's ftp files, so I guess I can start there. >> >> What I need: >> - Some indication about the first version of Pharo that I'm able to >> build purely from squeak-vm, and where to find its source code >> (git+version or commit if possible, I seem to only be able to find its >> binaries currently in phero's ftp files). >> - Any useful information for early bootstrap steps. >> >> Some useful information on my side: >> - During the build process in Guix, we can't download data, so the >> entire bootstrap chain has to be explicited at once, hence the need to >> go back to the beginning in this case. >> >> Thanks in advance! >> >> -- >> Best regards, >> Nicolas Graves > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes > > > > > -- Best regards, Nicolas Graves

May 21, 2024

Re: Info required for bootstrapping pharo on GNU Guix

by stephane ducasse

Hi Why canât you use the latest Pharo vm and Pharo12? We worked like mad over the years to get a much better system. Now why do you need to bootstrap Pharo because you can just use a bootstrapped image and get pharo working and running? S > On 21 May 2024, at 09:31, Nicolas Graves via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Hi Pharo community, > > I'm trying to package pharo in the GNU Guix linux distribution. Since > the distribution is focused on reproducibility and avoids using binary > code when possible, for that I need to reproduce the bootstrapping steps > that are embedded in Pharo. I understand from some developper online > comment that this is possible. > > I've started to work on this and it seems feasible, at least I get the > dependency loop, what I've some difficulty is to get precisely when it's > possible to get started. > > ------------------- > | v > pharo VM pharo > â§ | > ------------------- > > If I'm correct, > - bootstrapping is very clear after version ~7.0.0, and with a proper > build, just follow the distribution numbers in wget's with a cmake > build-system. > - for earlier versions, there's the repository > https://github.com/pharo-project/PharoBootstrap > that seems (git history) to be able to go back to Pharo 30. > - I understand that at some point, Squeak and Pharo used to have the > same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen > this is in Pharo's ftp files, so I guess I can start there. > > What I need: > - Some indication about the first version of Pharo that I'm able to > build purely from squeak-vm, and where to find its source code > (git+version or commit if possible, I seem to only be able to find its > binaries currently in phero's ftp files). > - Any useful information for early bootstrap steps. > > Some useful information on my side: > - During the build process in Guix, we can't download data, so the > entire bootstrap chain has to be explicited at once, hence the need to > go back to the beginning in this case. > > Thanks in advance! > > -- > Best regards, > Nicolas Graves StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 21, 2024

Re: Info required for bootstrapping pharo on GNU Guix

by stephane ducasse

Hi Why canât you use the latest Pharo vm and Pharo12? We worked like mad over the years to get a much better system. Now why do you need to bootstrap Pharo because you can just use a bootstrapped image and get pharo working and running? S > On 21 May 2024, at 09:31, Nicolas Graves via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Hi Pharo community, > > I'm trying to package pharo in the GNU Guix linux distribution. Since > the distribution is focused on reproducibility and avoids using binary > code when possible, for that I need to reproduce the bootstrapping steps > that are embedded in Pharo. I understand from some developper online > comment that this is possible. > > I've started to work on this and it seems feasible, at least I get the > dependency loop, what I've some difficulty is to get precisely when it's > possible to get started. > > ------------------- > | v > pharo VM pharo > â§ | > ------------------- > > If I'm correct, > - bootstrapping is very clear after version ~7.0.0, and with a proper > build, just follow the distribution numbers in wget's with a cmake > build-system. > - for earlier versions, there's the repository > https://github.com/pharo-project/PharoBootstrap > that seems (git history) to be able to go back to Pharo 30. > - I understand that at some point, Squeak and Pharo used to have the > same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen > this is in Pharo's ftp files, so I guess I can start there. > > What I need: > - Some indication about the first version of Pharo that I'm able to > build purely from squeak-vm, and where to find its source code > (git+version or commit if possible, I seem to only be able to find its > binaries currently in phero's ftp files). > - Any useful information for early bootstrap steps. > > Some useful information on my side: > - During the build process in Guix, we can't download data, so the > entire bootstrap chain has to be explicited at once, hence the need to > go back to the beginning in this case. > > Thanks in advance! > > -- > Best regards, > Nicolas Graves StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 21, 2024

Info required for bootstrapping pharo on GNU Guix

by Nicolas Graves

Hi Pharo community, I'm trying to package pharo in the GNU Guix linux distribution. Since the distribution is focused on reproducibility and avoids using binary code when possible, for that I need to reproduce the bootstrapping steps that are embedded in Pharo. I understand from some developper online comment that this is possible. I've started to work on this and it seems feasible, at least I get the dependency loop, what I've some difficulty is to get precisely when it's possible to get started. ------------------- | v pharo VM pharo â§ | ------------------- If I'm correct, - bootstrapping is very clear after version ~7.0.0, and with a proper build, just follow the distribution numbers in wget's with a cmake build-system. - for earlier versions, there's the repository https://github.com/pharo-project/PharoBootstrap that seems (git history) to be able to go back to Pharo 30. - I understand that at some point, Squeak and Pharo used to have the same VM. I have access to a squeak-vm 4.10.2.2614 in Guix, and I've seen this is in Pharo's ftp files, so I guess I can start there. What I need: - Some indication about the first version of Pharo that I'm able to build purely from squeak-vm, and where to find its source code (git+version or commit if possible, I seem to only be able to find its binaries currently in phero's ftp files). - Any useful information for early bootstrap steps. Some useful information on my side: - During the build process in Guix, we can't download data, so the entire bootstrap chain has to be explicited at once, hence the need to go back to the beginning in this case. Thanks in advance! -- Best regards, Nicolas Graves

May 21, 2024

This week (20/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 12 - Backport use of FormSet for ToggleMenuItemMorph submenu markers #16631 https://github.com/pharo-project/pharo/pull/16631 # Ehancements - [Enhancement] Add "copy class name" to extras menu in Calypse #16635 https://github.com/pharo-project/pharo/pull/16635 - Add missing RGGlobalVariable>>isInstanceVariable #16644 https://github.com/pharo-project/pharo/pull/16644 - Introduce CompiledMethod>>#isInstanceSide #16626 https://github.com/pharo-project/pharo/pull/16626 # Fixes - Issue 16430 - String>> asSymbol no protected against concurrent access (alternative solution) #16565 https://github.com/pharo-project/pharo/pull/16565 - [Bug]: Date>>#addMonths: should Respect Offset #16603 https://github.com/pharo-project/pharo/pull/16603 - sort subdirectories in the same order as the file tree table #748 https://github.com/pharo-spec/NewTools/pull/748 # VM - Fixed VirtualMachine 76 and 78 parameters #16641 https://github.com/pharo-project/pharo/pull/16641 - Do not retain any selectors in CogAbstractInstruction #798 https://github.com/pharo-project/pharo-vm/pull/798 - add tests for type harmonization #807 https://github.com/pharo-project/pharo-vm/pull/807 - remove warning because of type and unsigned shift issues #800 https://github.com/pharo-project/pharo-vm/pull/800 - Fixed ntb page selection change announcement if built without pages #1542 https://github.com/pharo-spec/Spec/pull/1542 # Package Structure - Sindarin/ScriptableDebugger should be listed as external project #16653 https://github.com/pharo-project/pharo/pull/16653 - Sindarin in Pharo13 need to be loaded from Pharo13 branch of ScriptableDebugger (and not Pharo12 branch) #751 https://github.com/pharo-spec/NewTools/pull/751 - Simplify Calypso packaging #16602 https://github.com/pharo-project/pharo/pull/16602 - Cleanup: CoverageCollectorTest should be in an own test package #16613 https://github.com/pharo-project/pharo/pull/16613 # Rules - proposition rule for nil branch #16547 https://github.com/pharo-project/pharo/pull/16547 - [Enhancement] Add a rule ReBaselineProperlyPackagedRule #16630 https://github.com/pharo-project/pharo/pull/16630 - [Enhancement] Add a rule ReBaselineWithProperSuperclassRule #16633 https://github.com/pharo-project/pharo/pull/16633 - proposition for a potential new rule: useless ifTrue:ifFalse: #16638 https://github.com/pharo-project/pharo/pull/16638 - add ReStatementsAfterReturnConditionalRule #16640 https://github.com/pharo-project/pharo/pull/16640 - Review ReClassNotCategorizedRuleTest>>#testRule #16649 https://github.com/pharo-project/pharo/pull/16649 - Improve ReBaselineProperlyPackagedRule and ReBaselineWithProperSuperclassRule and cover with tests #16648 https://github.com/pharo-project/pharo/pull/16648 - Enhancement: Provide a lint rule to check for a "super initialize" call in instance side #initialize methods #16615 https://github.com/pharo-project/pharo/pull/16615 - tests for rules from the General-Rules package #16474 https://github.com/pharo-project/pharo/pull/16474 # Cleanups - Reduce references to Undeclared global variable #16642 https://github.com/pharo-project/pharo/pull/16642 - Remove deprecated way to access the global package organizer #754 https://github.com/pharo-spec/NewTools/pull/754 - Remove the package Deprecated12, introduce package Deprecated13 #16538 https://github.com/pharo-project/pharo/pull/16538 - proposition refactoring -> Cleanup: 2 duplicated methods in FreeType #16583 https://github.com/pharo-project/pharo/pull/16583 - Clean up in SDL_Texture and SDL_Renderer #16601 https://github.com/pharo-project/pharo/pull/16601 - Simplify script pragma for FinderUI #16623 https://github.com/pharo-project/pharo/pull/16623 - CommentTestCase should be moved to PharoDocComment-Tests #16619 https://github.com/pharo-project/pharo/pull/16619 - Package "System-DependenciesTests" should be "System-Dependencies-Tests" #16621 https://github.com/pharo-project/pharo/pull/16621 - Cleanup: AthensTransformTest>>transformClass should be in accessing #16628 https://github.com/pharo-project/pharo/pull/16628 - Fix lint in ReShouldSendSuperSetUpAsFirstMessage class>>#checksMethod (second PR) #16643 https://github.com/pharo-project/pharo/pull/16643 - Remove part of ReAsClassRule about #asClass #16658 https://github.com/pharo-project/pharo/pull/16658 - Cleanup: Remove deprecated announcement #SnapshotDone in SnapshotOperation>>#performSnapshot for Pharo 13 #16657 https://github.com/pharo-project/pharo/pull/16657 - Cleanup: unnecessary class BlLoadProjectWorldMenu #16655 https://github.com/pharo-project/pharo/pull/16655 - SourceFile>>#isOpen should use isNotNil #16651 https://github.com/pharo-project/pharo/pull/16651 - Remove Gofer #16606 https://github.com/pharo-project/pharo/pull/16606 - Remove reference to a deprecated class #1822 https://github.com/pharo-vcs/iceberg/pull/1822 - Fixing call to deprecated code #749 https://github.com/pharo-spec/NewTools/pull/749 - Use isNotNil instead notNil in initializePresenters #753 https://github.com/pharo-spec/NewTools/pull/753 # Website - Update community.md: Social Media Section #74 https://github.com/pharo-project/pharo-website/pull/74 - Update community.md: update tweet suggestion form #73 https://github.com/pharo-project/pharo-website/pull/73 - Update Companies.md #72 https://github.com/pharo-project/pharo-website/pull/72 - Update 2024-04-26-pharo12-released.md: fix typy #69 https://github.com/pharo-project/pharo-website/pull/69

May 17, 2024

IWST Deadline Extension

by Guille Polito

Dear Community, Please let us inform you that the submission deadline for the full/short papers has been extended until May 31st, 2024 AoE. Let us remind you of the submission details: - Short position papers (5 to 10 pages) describing fresh ideas and early results. - Full papers (more than 10 pages) with deeper descriptions of experiments and research results. Please also consider that you may submit another work other than your original abstract. Paper accepted for publishing will be published within a *CEUR-WS Proceedings>https://ceur-ws.org/*. Hence, both submissions and final papers must be prepared using the *CEUR ART style>https://ceur-ws.org/Vol-XXX/CEURART.zip*. We recommend using the template in single-column style, although you may use two columns. CEUR proceedings accept papers in both styles as soon as they follow the template and have 5 or more pages. The IWST team, Gordana, Guille, and Steven https://esug.org/2024-Conference/IWST2024.html

May 17, 2024

[Website] updated forms to suggest companies and news entries

by Marcus Denker

Hi, I have updated two forms ob pharo.org 1) Companies using Pharo https://www.pharo.org/Companies 2) Suggest news https://www.pharo.org/community see the link in the Social Media section The forms for now have simple workflows attached to send emails to do the next step manually. Marcus

May 16, 2024