[Pharo-users] Re: [Esug-list] Re: [Pharo-dev] Re: [ANN] Soil release v1

> > But ground stone is just sand. There’s more than just sand in soil. Soil > should have the other ingredients needed for growth. :) I was trying to make a reference to a GemStone *stone *:) Dale On Wed, May 8, 2024 at 1:27 PM Norbert Hartl wrote: > > > Am 08.05.2024 um 16:14 schrieb

[Pharo-dev] Re: [Esug-list] Re: Re: [ANN] Soil release v1

> > But ground stone is just sand. There’s more than just sand in soil. Soil > should have the other ingredients needed for growth. :) I was trying to make a reference to a GemStone *stone *:) Dale On Wed, May 8, 2024 at 1:27 PM Norbert Hartl wrote: > > > Am 08.05.2024 um 16:14 schrieb

[Pharo-users] Re: [Esug-list] Re: [ANN] Soil release v1

> > To me as a non-native speaker it means: ground layer you can build/grow on Haha, Soil can also be thought of as "ground up stone" :) Dale On Wed, May 8, 2024 at 7:13 AM Norbert Hartl wrote: > > > Am 06.05.2024 um 16:47 schrieb Dirk Nel : > > I'll definitely check it out..! and for those

[Pharo-dev] Re: [Esug-list] Re: [ANN] Soil release v1

> > To me as a non-native speaker it means: ground layer you can build/grow on Haha, Soil can also be thought of as "ground up stone" :) Dale On Wed, May 8, 2024 at 7:13 AM Norbert Hartl wrote: > > > Am 06.05.2024 um 16:47 schrieb Dirk Nel : > > I'll definitely check it out..! and for those

[Pharo-dev] Re: Platform Packages vs. Git Branches

Max, Yeah, your approach looks manageable ... with a well defined common code base, both branch per platform (fuel) and platform packages (Grease) can be used ... I looked at your github action code and see that you've got a solution for triggering multi-branch runs ... workflow per

[Pharo-dev] Re: Platform Packages vs. Git Branches

I have some thoughts... Depending upon the pace of relative development keep in mind that merging changes between platform branches could present interesting problems whereas the package-based approach allows one to copy a method (if the algorithm is too platform-specific --- this the area where

[Pharo-dev] Re: Omnibase/Monibase repository removal

Here’s Kurt’s talk from Camp Smalltalk Supreme[1]. Dale [1] https://www.youtube.com/watch?v=uLF2S6fq5a4 Sent from my iPhone > On Aug 9, 2022, at 6:53 AM, Dale Henrichs > wrote: > > Norbert, > > I won’t be going to ESUG this year … travel to Europe has always been tough

[Pharo-users] Re: [Pharo-dev] Re: Omnibase/Monibase repository removal

Here’s Kurt’s talk from Camp Smalltalk Supreme[1]. Dale [1] https://www.youtube.com/watch?v=uLF2S6fq5a4 Sent from my iPhone > On Aug 9, 2022, at 6:53 AM, Dale Henrichs > wrote: > > Norbert, > > I won’t be going to ESUG this year … travel to Europe has always been tough

[Pharo-dev] Re: Omnibase/Monibase repository removal

t; Norbert > >> Am 08.08.2022 um 18:44 schrieb Dale Henrichs >> : >> >> Norbert, >> Before you go off and invent a data base, you might take a look at GemStone >> and RemoteServiceReplication[1] ... >> >> Dale >> >> [1] https://git

[Pharo-users] Re: [Pharo-dev] Re: Omnibase/Monibase repository removal

t; Norbert > >> Am 08.08.2022 um 18:44 schrieb Dale Henrichs >> : >> >> Norbert, >> Before you go off and invent a data base, you might take a look at GemStone >> and RemoteServiceReplication[1] ... >> >> Dale >> >> [1] https://git

[Pharo-dev] Re: Omnibase/Monibase repository removal

for something more lightweight and more easy to handle > approach this time. Well, from the github page I could not derive what it > really does to be honest. > > Hope to see you at ESUG, > > Norbert > >> Am 08.08.2022 um 18:44 schrieb Dale Henrichs >> : >> >

[Pharo-users] Re: [Pharo-dev] Re: Omnibase/Monibase repository removal

for something more lightweight and more easy to handle > approach this time. Well, from the github page I could not derive what it > really does to be honest. > > Hope to see you at ESUG, > > Norbert > >> Am 08.08.2022 um 18:44 schrieb Dale Henrichs >> : >> >

[Pharo-users] Re: [Pharo-dev] Omnibase/Monibase repository removal

ry or file per user (scaling), and no > additional server process(es) to be monitored for failure mode. > > Yanni > > On Mon, Aug 8, 2022 at 12:44 PM Dale Henrichs < > dale.henri...@gemtalksystems.com> wrote: > >> Norbert, >> Before you go off and invent a data base,

[Pharo-dev] Re: Omnibase/Monibase repository removal

Norbert, Before you go off and invent a data base, you might take a look at GemStone and RemoteServiceReplication[1] ... Dale [1] https://github.com/GemTalk/RemoteServiceReplication On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl wrote: > To all Omnibase and Monibase users. > > It turned out

[Pharo-users] Re: [Pharo-dev] Omnibase/Monibase repository removal

Norbert, Before you go off and invent a data base, you might take a look at GemStone and RemoteServiceReplication[1] ... Dale [1] https://github.com/GemTalk/RemoteServiceReplication On Mon, Aug 8, 2022 at 6:19 AM Norbert Hartl wrote: > To all Omnibase and Monibase users. > > It turned out

[Pharo-users] Re: Loading from a git repository with Metacello on a running seaside image

pdate my file system at iceberg/ > > Best > > Emilio > > On Thu, Apr 28, 2022 at 3:29 PM Dale Henrichs < > dale.henri...@gemtalksystems.com> wrote: > >> Emilio, >> >> I wasn't quite sure whether or not you were concerned about having the >> Baseline

[Pharo-users] Re: Loading from a git repository with Metacello on a running seaside image

ing. > It seems to be doing the load, but not the pull before the load. > > I had implemented no more than #baseLine: and now projectClass. > > If I go through the UI and do the pull it works perfectly. > Can I replicate that with a script? > > Best > > Emilio > &g

[Pharo-users] Re: Loading from a git repository with Metacello on a running seaside image

Emilio, Are you using a repository without Monticello meta data? If so, then you need to change the #projectClass of you your baseline to: > projectClass > Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | ^ cl > ]. > ^ super projectClass unless the #projectClass is

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

On 9/1/20 1:51 AM, Christophe Demarey wrote: Hi Dale, Thanks for the very detailed explanation. I updated the href link to only include the mcz file name. I also took the opportunity to display a nicer URL and set up a permanent redirection to the current mc repository folder (else links

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

On 8/30/20 3:07 AM, Christophe Demarey wrote: Hi Dale, Le 29 août 2020 à 19:40, Dale Henrichs <mailto:dale.henri...@gemtalksystems.com>> a écrit : So close, the interactive tests are passing, but there is a use case that is popping up in a travis job[1] where this

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

it will be fine. I removed the newline characters. I will also check if I can keep the original url in the browser rather than the redirected one. Regards, Christophe. Le 29 août 2020 à 18:41, Dale Henrichs <mailto:dale.henri...@gemtalksystems.com>> a écrit : Christophe, Again, I apprec

Re: [Pharo-users] Checking baseline before publishing

Esteban, #record _is_ run against the baseline that is in the image if it is present. This is true for all of the Metacello commands - if the BaselineOf is present it is used, if it is not present it will be loaded. The #get command will load a fresh copy of the baseline from the repository.

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

Christophe, I appreciate your effort, but I assume that you aren't finished yet? When I use the url from your message I get a `Not Found` error (note that I explicitly included a trailing slash in the url): This is a bug (or omission) as well, since other Monticello sites produce the

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

to always assume the client is Pharo, while the dynamic version used format=raw (which non-Pharo implementation did not include in their request for the listing) to send the Pharo specific response only then. On 27 Aug 2020, at 23:34, Dale Henrichs wrote: Depends upon how old that optimized code

Re: [Pharo-dev] 'VOMongoConnectionError' when dowloading mcz from smalltalkhub.com

attributes: { #href. each } with: each ] ] ] ] ] Sven On 27 Aug 2020, at 22:29, Dale Henrichs wrote: My guess is lies in the difference in the payload returned. http://www.squeaksource.com/MooseSQL/ produces a html

Re: [Pharo-users] smalltalkhub down

... and it is still down today ... having smalltalkhub down is starting to interfere with builds, hopefully we won't have to wait too long for the problem to be resolved ... Dale On 7/10/20 2:59 PM, PAUL DEBRUICKER wrote: https://downforeveryoneorjustme.com/smalltalkhub.com

Re: [Pharo-users] Resources Page

I think the free license is contingent upon having contributed to an open source project. Also there appears to be free trial version[1]. Dale [1] https://www.instantiations.com/products/vasmalltalk/download.html On 1/28/20 5:25 PM, Richard Sargent wrote: Thanks. On Tue, Jan 28, 2020, 17:21

Re: [Pharo-users] Old projects in ss3

Thanks Carlo ... that will certainly help me solve this problem ... I probably won't be able to get ss3 patched until after ESUG :), but now I know where to look ... Dale On 8/10/19 3:20 PM, sk via Pharo-users wrote: Hi Dale Looks like a NumberParser error due to the chrome Accept request

[Pharo-dev] (7.0.3) writing a large(?) string to stdout is mangled

I've run into an issue with pharo 7.0.3 where writing a string that contains embedded crs or lfs to stdout causes the output to be corrupted in odd ways. I have provided the details and a reproducible test case up on github[1]. Stef suggested I post the issue here as well ... Dale [1]

Re: [Pharo-users] Can I control the location of the PharoDebug.log

On 8/7/19 11:32 AM, Torsten Bergmann wrote: Dale wrote: I used the double click trick on "Log file name" and followed it to the above messages for the records: Beside double click you can also right click on a setting and select "Browse" to find where it is implemented. You can then also

Re: [Pharo-users] Can I control the location of the PharoDebug.log

.     GTGenericStackDebugger logDebuggerStackToFile: false. While writing this message I found that there does appear to be a setting that controls this (I used the double click trick on "Log file name" and followed it to the above messages), but I haven't actually tested it:): On 7/31/19 4:58 PM, Dale Henr

Re: [Pharo-users] more fun with System>>Local directory settings

Thanks for the sample code! ... I keep forgetting that a scan of allInstances is a good way to patch problems like these:) and the fixed to relative path snippet is especially useful. Dale On 8/1/19 1:50 PM, Sean P. DeNigris wrote: Dale Henrichs-3 wrote the act of starting the image

[Pharo-users] Can I control the location of the PharoDebug.log

It appears that the PharoDebug.log can be dropped into the directory from which a Pharo image is launched ... I would have expected it to be dropped into the local directory, but that does not appear to be the case ... I've looked in the Settings Browser and there does not appear to be a way

Re: [Pharo-users] where are system settings stored?

On 7/22/19 10:30 AM, Cyril Ferlicot wrote: FileLocator preferences asFileReference Thanks Cyril ... I get `File @ /home/dhenrich/.config` and there is a pharo directory with some stuff in it ... poking around it seems that the system settings are in a pharo/7.0 subdirectory with a

[Pharo-users] where are system settings stored?

I am currently using Pharo 7.0 and I've just discovered that my "local directory" is /home/dhenrich/rogue/_homes/rogue/_home/dev/clients/gci_70_tst/pharo-local: This file has to date back to the beginning of the year and i had deleted that directory structure a week or so ago before starting

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

SETT was create based on our understanding (GemTalk Systems) of what the tonel disk format was _supposed_ to be and I think that Pharo has departed from somewhat from what was understood to be the format. I've had similar problems trying to use filetree repositories with Iceberg that have

Re: [Pharo-dev] FW: Versioning with Iceberg

Haha, I agree! Dale On 6/3/19 11:06 AM, ducasse wrote: We will make it :) Stef This is our goal as well... Dale On 6/1/19 6:37 AM, ducasse wrote: My goal is to have the best environment possible and I’m working to make it. My goal is not to have a smalltalk system compatible with the

Re: [Pharo-dev] FW: Versioning with Iceberg

This is our goal as well... Dale On 6/1/19 6:37 AM, ducasse wrote: My goal is to have the best environment possible and I’m working to make it. My goal is not to have a smalltalk system compatible with the rest of the universe. Now since people deploy on Gemstone we will pay attention to them

Re: [Pharo-users] [gemstones] Use case for GsDevKit_home

On 5/30/19 11:12 AM, sergio ruiz wrote: Whew… hefty.. digging into this now.. Haha ... this is why backup and restore functionality has been built into tODE:) and GsDevKit_home ... Dale

Re: [Pharo-dev] Smalltalk to Smalltalk interface

On 5/30/19 11:09 AM, ducasse wrote: I know that people some people ported STON to VW and used it to be able to build nice new systems in Pharo while talking to their old software in VW. So this is a nice way to migrate :) STON has also been ported to GemStone and likely to be ported to VA as

Re: [Pharo-users] [gemstones] Use case for GsDevKit_home

On 5/30/19 6:58 AM, James Foster wrote: On May 30, 2019, at 5:44 AM, sergio ruiz > wrote: ... Also, one thing that I find invaluable in troubleshooting applications written using relational databases is to be able to be able to just dump the production

Re: [Pharo-users] [gemstones] Use case for GsDevKit_home

On 5/30/19 5:44 AM, sergio ruiz wrote: I have another project coming up, and I have free reign over the tech stack. I am gonna use Pharo, but I'd like to spend my up front time on this project figuring out the things I usually wait until the end to do. One of these issues is setting up

Re: [Pharo-users] [GsDevKit_home] Is this project still the way to set up Gemstone?

Sergio, Also include the SHA of the GsDevKit_home commit that you are using: cd $GS_HOME git log -1 Dale On 5/29/19 5:39 PM, Dale Henrichs wrote: Sergio, Could you open an issue here[1]. This is purely a GsDevKit_home issue. When you submit the issue, could you include details

Re: [Pharo-users] [GsDevKit_home] Is this project still the way to set up Gemstone?

Sergio, Could you open an issue here[1]. This is purely a GsDevKit_home issue. When you submit the issue, could you include details about what hardware you are running on and it would help if you included the entire install.log in your issue report as I think there is additional information

Re: [Pharo-users] How to visit over packages, classes, methods (all types)

clarification embedded below On 5/20/19 3:43 PM, Dale Henrichs wrote: | project className | project := (Rowan projectNamed:'Exercise') asDefinition. className := 'Acronym'. packageName := 'Exercise-', className. ((project addPackageNamed: packageName

Re: [Pharo-users] How to visit over packages, classes, methods (all types)

baseline-complexity-of-tiny-big-projects-td5099495.html Tim Sent from my iPhone On 20 May 2019, at 20:16, Dale Henrichs <mailto:dale.henri...@gemtalksystems.com>> wrote: Tim, I know that this doesn't answer your question, but one of the features that I'm building into Rowan i

Re: [Pharo-users] How to visit over packages, classes, methods (all types)

Tim, I know that this doesn't answer your question, but one of the features that I'm building into Rowan is just this capability: * project definitions composed of package definitions * package definitions composed of class and class extension definitions * class and class extensions

Re: [Pharo-users] How to make Metacello ignore package cache?

be using a BaselineOf with a git repository ... Dale On 4/26/19 11:11 AM, Hernán Morales Durand wrote: Hi Dale, El vie., 26 abr. 2019 a las 15:12, Dale Henrichs () escribió: I'm not exactly sure why you are getting the error, but the standard way to deal with a package-cache issue (or at least

Re: [Pharo-users] How to make Metacello ignore package cache?

I'm not exactly sure why you are getting the error, but the standard way to deal with a package-cache issue (or at least eliminate the package-cache as the real culprit) is to clear the package-cage in the Monticello browser ... An alternative (or next step) would be to try the following:

Re: [Pharo-users] Baseline subclasses

package. The project is not for public consumption so we have to do that in our deployment process nowhere else. Norbert Am 25.04.2019 um 09:51 schrieb Norbert Hartl <mailto:norb...@hartl.name>>: Am 25.04.2019 um 01:13 schrieb Dale Henrichs <mailto:dale.henri...@gemtal

Re: [Pharo-users] Baseline subclasses

On 4/24/19 3:08 PM, Norbert Hartl wrote: I don‘t have an idea how to achieve this with a group. It is about changing the number of dependencies of one package. There's load order and there's grouping... If you are using #linear loads for a BaselineOf then hard dependencies (Metacello

Re: [Pharo-users] Baseline subclasses

Do I understand you correctly that the BaselineOfWhiteLabelProduct is a subclass of BaselineOfCoreProduct? If so, I have no idea what would happen and it certainly has never been tested ... and as I think about this I can see that there would definitely be problems ... I think you are lucky

Re: [Pharo-users] Why doesn't collection have #excludes (the mirror of includes)?

Isn't this an "ultimate" goal for Pharo  ... once you've got a stable (truly) minimum image, custom class libraries are possible if not desirable ... Dale On 3/18/19 11:08 AM, Esteban Maringolo wrote: El dom., 17 mar. 2019 a las 6:33, Sven Van Caekenberghe () escribió: On 17 Mar 2019, at

Re: [Pharo-users] How exactly is "share repositories between images" supposed to work without tripping each other up?

On 3/6/19 8:18 AM, Sean P. DeNigris wrote: Tim Mackinnon wrote how is this shared repository supposed to work? While I initially liked the space efficiency of the shared approach, I eventually gave up because it created too many (often obscure) problems. It just doesn't seem to be a good

Re: [Pharo-users] Trying to understand Developing with Pharo, Deploying with Gemstone/s

Hello Sergio, Sorry for the delay in replying .. too many balls in the air:) I'll comment in-line .. On 2/8/19 7:07 AM, sergio ruiz wrote: I have an app that is ready to deploy to alpha. I usually do this by creating a script that builds a minimal pharo image, and run that on a cloud

Re: [Pharo-users] [ANN] SETT (Store Export to Tonel Tools) for Pharo6.1

A. Maringolo El mié., 16 ene. 2019 a las 18:18, Dale Henrichs via Pharo-users (mailto:pharo-users@lists.pharo.org>>) escribió: On 1/16/19 11:56 AM, Esteban Maringolo wrote: This is great! One less fence to move code from one dialect to another. :) I will follow the examples a

Re: [Pharo-dev] How does Metacello decide what is already loaded ?

On 2/14/19 11:28 AM, Sven Van Caekenberghe wrote: OK, where is the registry, how does it work, where can I read about it ? `MetacelloProjectRegistration registry` ... It is a private registry of loaded baselines and configurations used by Metacello. It's been around roughly 6-7 years or so

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

o/bin/pharo-vm' $ ../bin/pharo Pharo.image eval 'FileLocator vmBinary pathString' '/home/t3/pharo/bin/pharo-vm/pharo' > On 25 Jan 2019, at 18:25, Dale Henrichs mailto:dale.henri...@gemtalksystems.com>> wrote: > > Thanks Nicolas, > > Is i

Re: [Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

and document it. And if we can't reasonably document it, then we might want to open an issue on opensmalltalk. Le ven. 25 janv. 2019 à 01:51, Dale Henrichs <mailto:dale.henri...@gemtalksystems.com>> a écrit : I am in the process of porting the GemStone-GCI[1] project to

[Pharo-dev] naming convention for pharo-vm/lib/pharo/* directory?

I am in the process of porting the GemStone-GCI[1] project to Pharo6.1 (32 bit) and Pharo7.0 (64 bit) and I'm curious what the naming convention for the library directories are. For Pharo5.0 and earlier, I copied my 32 bit gemstone gci library files (.so on linux) into the pharo-vm directory.

Re: [Pharo-users] [ANN] SETT (Store Export to Tonel Tools) for Pharo6.1

and it looks like the current code base is wired to use Unix[1] Dale [1] https://github.com/GemTalk/SETT/blob/master/StoreImporter.package/SettGitRepository.class/instance/runGitWithArguments..st Esteban A. Maringolo El mié., 16 ene. 2019 a las 16:38, Dale Henrichs (<mailto:dale.he

[Pharo-users] [ANN] SETT (Store Export to Tonel Tools) for Pharo6.1

GemTalkSystems is pleased to announce SETT (Store Export to Tonel Tools)[1]. SETT is open source project with an MIT license. SETT (Store Export to Tonel Tools) is a set of tools to export Smalltalk code from Store and write into the Tonel file format managed using Git. SETT is: * a Pharo

Re: [Pharo-users] Updating singletons

Konrad, Did you try what I suggested and did it solve your problem? Dale On 1/5/19 2:45 AM, Konrad Hinsen wrote: Dale, This looks like a case where you are using a metadata-less repository ... if so you, should add the following method to your baseline class: Sorry, that's way above my

Re: [Pharo-users] Updating singletons

Konrad, This looks like a case where you are using a metadata-less repository ... if so you, should add the following method to your baseline class: projectClass Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | ^ cl ]. ^ super projectClass This mod will

Re: [Pharo-users] how to write this without a if then

Roelof, One technique to eliminating the use of #ifTrue:ifFalse: is to use double dispatching. There are some good examples of using double dispatching in Ralph Johnson's paper "ARITHMETIC AND DOUBLE DISPATCHING IN SMALLTALK-80"[1].  you should be able to get the basic idea by skimming the

Re: [Pharo-users] Metacello load baselines/configurations only

Use the Metacello `get` command:     Metacello new         repository: '...';         get Just the baseline (or Configuration) will be loaded. Dale On 10/02/2018 11:34 PM, Peter Uhnak wrote: Hi, is there a way to instruct Metacello to only install BaselineOfs/ConfigurationOfs instead of

Re: [Pharo-dev] Metacello locking system

On 03/06/2018 10:51 AM, Cyril Ferlicot D. wrote: Cyril, For development I tend to use Metacello locking instead of hard-wired dependencies in the BaselineOf and that works very well --- it completely avoids the need to edit a baseline for development purposes and this approach works really

Re: [Pharo-dev] Released versions in Pharo Bootstrap

On 03/06/2018 06:21 AM, Guillermo Polito wrote: Hi Dale! On Mon, Mar 5, 2018 at 8:07 PM, Dale Henrichs <dale.henri...@gemtalksystems.com <mailto:dale.henri...@gemtalksystems.com>> wrote: On 03/05/2018 09:07 AM, Guillermo Polito wrote: On the other side, there

Re: [Pharo-dev] Released versions in Pharo Bootstrap

On 03/05/2018 11:22 AM, Stephane Ducasse wrote: In an image where you want to use the dev_pharo7 for a project, you do a Metacello lock on github:///xxx:dev_pharo7/src BEFORE loading the project ... if there are multiple projects that need to all coordinate development then you follow the

Re: [Pharo-dev] Released versions in Pharo Bootstrap

That's fine ... but then it should be a separate thread ... Dale On 03/05/2018 11:16 AM, Stephane Ducasse wrote: Dale no private emails please. stef On Mon, Mar 5, 2018 at 6:57 PM, Dale Henrichs <dale.henri...@gemtalksystems.com> wrote: Cyril, For development I tend to use Met

Re: [Pharo-dev] Released versions in Pharo Bootstrap

velopment_ together ... Dale [1] https://github.com/Metacello/metacello/blob/master/docs/LockCommandReference.md#lock-command-reference On 03/05/2018 10:18 AM, Denis Kudriashov wrote: Hi Dale. Where to read about locking? 2018-03-05 18:57 GMT+01:00 Dale Henrichs <dale.henri...@gemta

Re: [Pharo-dev] Released versions in Pharo Bootstrap

On 03/05/2018 09:07 AM, Guillermo Polito wrote: On the other side, there is the fact that Metacello baselines are so far nice to describe release project dependencies, but they are not so nice to describe subprojects/development dependencies that may get edited along with the parent project.

Re: [Pharo-dev] Released versions in Pharo Bootstrap

On 03/05/2018 08:48 AM, Stephan Eggermont wrote: teso...@gmail.com wrote: Hello, i have seen in the latest version of Pharo baselines pointing to "floating" versions. A version that is not fixed. I want to know why this is like that? Because that is the way it

Re: [Pharo-dev] Released versions in Pharo Bootstrap

Cyril, For development I tend to use Metacello locking instead of hard-wired dependencies in the BaselineOf and that works very well --- it completely avoids the need to edit a baseline for development purposes and this approach works really well for me ... perhaps we can discuss this in

Re: [Pharo-dev] How to use git with gitfiletree

On 03/02/2018 10:14 AM, Sean P. DeNigris wrote: Peter Uhnák wrote you mean that gitFILETREE:// would somehow use TONEL? No, I mean a configuration file specifying tonel, like we currently have .filetree files in every directory with filetree things in it. Embedding the serialization format

Re: [Pharo-dev] How to use git with gitfiletree

Esteban and I have agreed on some new url patterns (and changes to Tonel)  that should make things easier, however, neither of us has had the time to implement the features ... so I guess I can only say that you need to be patient (and use whatever workarounds that apply) until these new

Re: [Pharo-users] How to specify generic (non-github) git dependency?

Herby, Right now there is "no portable way" to specify arbitrary hosts in a Metacello spec ... but Esteban and I will be talking about this on Monday ... Thierry Goubier seems to have a nice scheme for gitfiletree and I think that iceberg might support additional urls and schemes... Dale

Re: [Pharo-users] unsolicited package-cache use

It could be out of sync. Le 18/01/2018 à 15:22, Dale Henrichs a écrit : Hilaire, Metacello just uses Monticello for loading and it is Monticello that is using the package-cache ... if there were a way to turn of the package-cache for Monticello I don't think that Metacello would know the

Re: [Pharo-users] unsolicited package-cache use

Hilaire, Metacello just uses Monticello for loading and it is Monticello that is using the package-cache ... if there were a way to turn of the package-cache for Monticello I don't think that Metacello would know the difference. But, I am curious why you care whether or not package is used?

Re: [Pharo-dev] Tonel code?

ion to private email if you are more comfortable with that - and perhaps our conversation can form the basis of a wiki? Dale https://github.com/dalehenrich/CypressReferenceImplementation On Sun, Jan 14, 2018 at 2:20 PM, Dale Henrichs <dale.henri...@gemtalksystems.com <mailto:dale.h

[Pharo-dev] a summary of the "blame" thread

The recent "blame" thread seems to have touched on a sore point for some folks and the discussion has devolved into a melee of clashing  (s)words -- which in general is pretty counter-productive. I read through each of the messages in the thread and tried to pick out the concrete

[Pharo-dev] git and author/timestamps, 10000's of files, etc.

I've been skimming the ironically named "blame" thread and just want to clear up some apparent misconceptions. git/github is not the reason that the author/timestamps information was "lost" ... when tonel was introduced the author/timestamp info was not included in the format as a separately

Re: [Pharo-dev] Tonel code?

Javier, I have a port of Tonel to GemStone[1] that runs against both Monticello and CypressReferenceImplementation[2]. I have yet to merge my work back into pharo-vcs/tonel, because I'm waiting for Tonel to stabilize and well ... I'm also busy:). It might be useful for you to see how I've

Re: [Pharo-dev] Flexibility of ZnUrl (For Metacello evolution)

On 12/29/17 3:55 AM, Sven Van Caekenberghe wrote: On 29 Dec 2017, at 10:35, Cyril Ferlicot D. wrote: Hi, In order to improve the usage of Pharo and the git integration there is some discussions around Metacello in order to be able to: - Load a private git

Re: [Pharo-users] Metacello with Git

d on to be available ... On Tue, Dec 19, 2017 at 4:49 PM, Dale Henrichs <dale.henri...@gemtalksystems.com <mailto:dale.henri...@gemtalksystems.com>> wrote: BitBucket is supported with like Github with: butbucket:///. With regards to GitLab, their download zip format is/was dif

Re: [Pharo-users] Metacello with Git

Sean, I am under the impression that iceberg is able to authenticate with SSH keys I am not a pharo/iceberg user myself, but it seems that iceberg should be able to fill that gap. Dale On 12/19/17 7:02 PM, Sean P. DeNigris wrote: CyrilFerlicot wrote For bitbucket you can use

Re: [Pharo-users] Metacello with Git

BitBucket is supported with like Github with: butbucket:///. With regards to GitLab, their download zip format is/was different enough from BitBucket/Github to make it difficult to provide the same level of support. See the series of comments here[1]. When the github:// was first introduced

Re: [Pharo-dev] [Pharo 7.0-dev] Build #332: 20759 Unused temps in Metacello classes

Sorry for the delay ... I am looking at merging this issue into Metacello ... a couple failed tests need to be rerun to see where we stand ... On 11/27/17 12:54 PM, Torsten Bergmann wrote: Yes - I submitted a PR to Metacello too: https://github.com/Metacello/metacello/pull/473 Who is able

Re: [Pharo-dev] Metacello we need automated conflict resolution between Baselines and Configurations

to make up their minds and SmalltalkCI needs to expose the conflict resolution api for Metacllo ... Dale Thanks, Peter On Thu, Nov 9, 2017 at 11:17 PM, Dale Henrichs <dale.henri...@gemtalksystems.com <mailto:dale.henri...@gemtalksystems.com>> wrote: Peter, Metacello locks a

Re: [Pharo-dev] Metacello we need automated conflict resolution between Baselines and Configurations

Peter, Metacello locks are supposed to address this kind of problem ... at this point in time, any project that is loaded from a git project should be 'locked' using a Metacello lock. The lock means that any request to load that project will use the locked version instead of the version

Re: [Pharo-dev] Zinc and Zodiac - Synching/Contributing

On 10/28/17 3:27 AM, Sven Van Caekenberghe wrote: On 28 Oct 2017, at 11:39, Norbert Hartl wrote: Am 28.10.2017 um 11:21 schrieb Sven Van Caekenberghe : Torsten, On 26 Oct 2017, at 19:12, Torsten Bergmann wrote: Hi Sven, for Zinc

Re: [Pharo-dev] [IMPORTANT] Is there a bug in Tonel with category:

properly ... Dale [1] https://github.com/GsDevKit/tonel/commit/b00565685586630452a9de3d4f90f16571428019#diff-bf8f5ba630dc8c679c3c68668bc76a5e On 11/6/17 11:15 AM, Dale Henrichs wrote: On 11/06/2017 08:23 AM, Sven Van Caekenberghe wrote: On 6 Nov 2017, at 17:13, Dale Henrichs <dale.he

Re: [Pharo-dev] [IMPORTANT] Is there a bug in Tonel with category:

On 11/06/2017 08:23 AM, Sven Van Caekenberghe wrote: On 6 Nov 2017, at 17:13, Dale Henrichs <dale.henri...@gemtalksystems.com> wrote: On 11/6/17 7:07 AM, Sven Van Caekenberghe wrote: On 6 Nov 2017, at 15:43, Dale Henrichs <dale.henri...@gemtalksystems.com> wrote: of course

Re: [Pharo-dev] [IMPORTANT] Is there a bug in Tonel with category:

On 11/6/17 7:07 AM, Sven Van Caekenberghe wrote: On 6 Nov 2017, at 15:43, Dale Henrichs <dale.henri...@gemtalksystems.com> wrote: of course with Pharo's implementation of Symbol it is not practical to use asString nor type checks - things that are not necessary in other Sma

Re: [Pharo-dev] [IMPORTANT] Is there a bug in Tonel with category:

...also note that I have seen a number of baselines where symbols are used in places where Strings are required ... of course with Pharo's implementation of Symbol it is not practical to use asString nor type checks - things that are not necessary in other Smalltalk implementations ... In

Re: [Pharo-dev] Baseline/Configuration loading bars

:18 AM, Stephane Ducasse wrote: Hi dale I'm confused :) what we should do? I could not get it (ok I'm a doct waiting room so not a super place to check). Stef On Wed, Nov 1, 2017 at 4:43 PM, Dale Henrichs <dale.henri...@gemtalksystems.com> wrote: Ben, I took a look at this and Metacell

Re: [Pharo-dev] Baseline/Configuration loading bars

Ben, I took a look at this and Metacell has wrapped the load expressions with a MetacelloPlatform>>do:displaying: call that presumably is supposed to show the progress bars continuously during a Metacello load, but a check in Pharo3.0 shows that the Pharo platform class don't override the

Re: [Pharo-users] How to include DeployUtils in a Configuration?

Hernán. Well I tried to look at this, but the first problem I ran into is that the package name is a Symbol (#ConfigurationOfSystemLogger) and the package name is supposed to be a String --- I'm trying to look at this from GemStone --- the package name is also a Symbol (#DeployUtils), so I

Re: [Pharo-users] Some Metacello issue

On 06/07/2017 03:46 AM, Holger Freyther wrote: On 7. Jun 2017, at 14:09, Stephan Eggermont wrote: Never refer to fixed versions unless you know why (you need to avoid a specific bug fix). When wanting to have repeatable builds (e.g. for bugfixes) and in the absence of

Re: [Pharo-dev] Github package management beta

dhenr...@gemtalksystems.com On 06/06/2017 09:32 PM, Eliot Miranda wrote: Hi All, I've been invited to participate in github's Bera test of their new package management support. I don't know much, if anything, about the software except that it supports RubyGems (Ruby), Maven (Java) and

  1   2   3   4   5   6   7   8   9   10   >