Re: [Pharo-dev] I love the launcher!!!!

I liked the launcher a lot, but It took me a while to get a version working out-of-the-box on Ubuntu. It's not available with the VM on the /download page for Linux. My preferred choice would be the PPA anyway, as I like to keep stuff under APT control, but I had to dig a lot to find a

Re: [Pharo-dev] I love the launcher!!!!

demarey wrote > Maybe it could be related to this bug: > https://github.com/pharo-project/pharo-launcher/issues/52 It is a different bug in the same behavior. The easy workaround is to manually create a pharo.version file for the offending image. As to the bug… The immediate problem turned

Re: [Pharo-dev] [ANN] files.pharo.org server move tomorrow, Nov 30

Maybe a good occasion to fix opensmalltalk-vm :) i.e. https://ci.appveyor.com/project/OpenSmalltalk/vm/branch/Cog/job/h8la5cg9fi2t3l2s /cygdrive/c/projects/vm/deploy/pharo %CYG_ROOT%\bin\bash -lc "cd $APPVEYOR_BUILD_FOLDER/deploy/pharo; exec 0: > Hi, > > We will do the switch to the new server

[Pharo-dev] [ANN] files.pharo.org server move tomorrow, Nov 30

Hi, We will do the switch to the new server tomorrow, Nov 30. -> for people downloading, there should be no service intererruption -> For *uploaders* (mostly CI jobs), you need new SSH credentials. This means some upload jobs might break, but they will be easy to fix -> Uploading humans

Re: [Pharo-dev] I love the launcher!!!!

demarey wrote > Yes, I'm able to run pharo 1.4 images. Hmm, when I tried to launch a 1.4 image, it hung forever while "Determining image version". I interrupted and manually run the command on the terminal: "/Users/sean/Documents/Pharo/vms/private/6505/Pharo.app/Contents/MacOS/Pharo"

Re: [Pharo-dev] Iceberg workflow

Ben Coman wrote > That is cool to automate that, but these names seem a bit generic to > take ownership across all domains in random projects. I may have explained poorly. It merely guesses a default value in the repo creation form. One is free to change manually as always if needed. -

Re: [Pharo-dev] I love the launcher!!!!

Unfortunately this fix did not work. Details are described in https://github.com/pharo-project/pharo-launcher/issues/55 Meanwhile I fixed it in an own commit: PharoLauncher-Core-TorstenBergmann.146 Launcher is now able to give the filter pattern not as global regex but now specific to the

[Pharo-dev] [Pharo 7.0-dev] Build #350: 20782-CompiledCode-misses-an-abstract-sourcePointer-method

There is a new Pharo build available! The status of the build #350 was: SUCCESS. The Pull Request #561 was integrated: "20782-CompiledCode-misses-an-abstract-sourcePointer-method" Pull request url: https://github.com/pharo-project/pharo/pull/561 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #349: -20785/Fix-the-names-of-uploaded-bootstrap-zip-files

There is a new Pharo build available! The status of the build #349 was: SUCCESS. The Pull Request #563 was integrated: "-20785/Fix-the-names-of-uploaded-bootstrap-zip-files" Pull request url: https://github.com/pharo-project/pharo/pull/563 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #348: 20783-upload-temporary-building-files-into-a-separate-repository

There is a new Pharo build available! The status of the build #348 was: SUCCESS. The Pull Request #562 was integrated: "20783-upload-temporary-building-files-into-a-separate-repository" Pull request url: https://github.com/pharo-project/pharo/pull/562 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #347: 20777-Fix-instVarAt-instVarAt-put-comment

There is a new Pharo build available! The status of the build #347 was: SUCCESS. The Pull Request #559 was integrated: "20777-Fix-instVarAt-instVarAt-put-comment" Pull request url: https://github.com/pharo-project/pharo/pull/559 Issue Url: https://pharo.fogbugz.com/f/cases/20777 Build

Re: [Pharo-dev] VoxelSpace

> On 29 Nov 2017, at 10:41, Pavel Krivanek wrote: > > The problem is in the wrong Metacello version in Pharo 6.1 that has no proper > Tonel support. It should be fixed with the next Iceberg update in Pharo 6.1. not really. it should be fixed with the next

Re: [Pharo-dev] Iceberg workflow

On 28-11-17 22:08, Torsten Bergmann wrote: Having the code directly in the root is possible but not a good style or to be recommended - because often projects include more than just the source code and over time include more and more things like docu or other. Thanks for the explanation for

Re: [Pharo-dev] Iceberg workflow

> On 29 Nov 2017, at 07:19, Ben Coman wrote: > > On 29 November 2017 at 07:50, Sean P. DeNigris wrote: >> Stephan Eggermont-3 wrote 2c) Code subdirectory: enter "src" here !!! >>> Do we really need that? Why would I care about that? >>

Re: [Pharo-dev] Iceberg workflow

> On 29 Nov 2017, at 06:51, Ben Coman wrote: > > On 29 November 2017 at 02:40, Torsten Bergmann wrote: >> Hi Ben, >> >> I think you forgot to give Iceberg the "src" subdirectory where all the code >> packages reside. > > Not such much forgot and not

Re: [Pharo-dev] Iceberg workflow

> On 28 Nov 2017, at 22:08, Torsten Bergmann wrote: > > You do not have to use "src" or "repository" - you can store your packages > directly in the root if you > like. You are free to choose. But over time it can "bloat" the topmost level > of your project with the >

Re: [Pharo-dev] Iceberg workflow

> On 28 Nov 2017, at 20:25, stephan wrote: > > On 28-11-17 19:40, Torsten Bergmann wrote: >> 2c) Code subdirectory: enter "src" here !!! > > Do we really need that? Why would I care about that? because you want to structure your projects as you want, and not as some

Re: [Pharo-dev] Iceberg workflow

> On 28 Nov 2017, at 19:40, Torsten Bergmann wrote: > > Hi Ben, > > I think you forgot to give Iceberg the "src" subdirectory where all the code > packages reside. > When you forget to give the "Code subdirectory" in the dialog the repo points > to the >

Re: [Pharo-dev] Iceberg workflow

Hi Ben, we have been discussing a lot this issues in discord recently (expectations from git users, monticello users and what iceberg needs to do/show in which case). basically, we have a mess on terminology and some workflows needs to be enhanced. Now, about your observations: a) more

Re: [Pharo-dev] I love the launcher!!!!

Hi Torsten, I think I have a fix for your problem. I opened an issue fot it: https://github.com/pharo-project/pharo-launcher/issues/55. Could you confirm if it is ok now? > Le 28 nov. 2017 à 20:11, Torsten Bergmann a écrit : > > Hi, > > Launcher is a power tool and has helped

Re: [Pharo-dev] I love the launcher!!!!

> Le 28 nov. 2017 à 21:53, Volkert a écrit : > > > > On 28.11.2017 17:33, Christophe Demarey wrote: >> Hi, >> >> >>> Le 25 nov. 2017 à 21:45, Volkert a écrit : >>> >>> The PharoLauncher is really nice ... >>> >>> Is it

Re: [Pharo-dev] I love the launcher!!!!

> Le 29 nov. 2017 à 00:52, Sean P. DeNigris a écrit : > > demarey wrote >>> pre Pharo-5 image >> It probably means that the command used to determine the image version >> failed! > > Oh, are Pharo 4 and prior supposed to work? I figured they were just not > intended to