Op 8-11-2017 om 15:56 schreef stephan:
I run into all kinds of issues with the directory structure used by the
new PharoLauncher.
When I copy an image with the launcher, how can I synchronize the
Iceberg repositories again? Do I just need to copy the original
directory containing them? Is
On 9 November 2017 at 10:18, Guillermo Polito wrote:
>
> An analysis of the situation so people out of context can understand better
> the forces in play here :)
>
> - Working directory and files constant property: files defined using a
> *relative path* are created
Thanks Christophe!!!
On Thu, Nov 9, 2017 at 9:02 PM, Christophe Demarey
wrote:
> thanks
>
>> Le 9 nov. 2017 à 20:10, stephan a écrit :
>>
>> On 09-11-17 11:49, Christophe Demarey wrote:
>>> Stephan, could you open an issue for that on GH?
>>
>>
thanks
> Le 9 nov. 2017 à 20:10, stephan a écrit :
>
> On 09-11-17 11:49, Christophe Demarey wrote:
>> Stephan, could you open an issue for that on GH?
>
> https://github.com/pharo-project/pharo-launcher/issues/51
>
> Stephan
>
>
>
On 09-11-17 11:49, Christophe Demarey wrote:
Stephan, could you open an issue for that on GH?
https://github.com/pharo-project/pharo-launcher/issues/51
Stephan
> Le 9 nov. 2017 à 10:18, Guillermo Polito a écrit :
>
> - launching Pharo from the pharo launcher (taken from this thread)
> Apparently the pharo launcher is launching the image from a
> directory internal to the launcher.
In the Pharo launcher, I
On 09-11-17 10:18, Guillermo Polito wrote:
An analysis of the situation so people out of context can understand
better the forces in play here :)
Thanks Guille, that clears up a number of my misunderstandings
Stephan
An analysis of the situation so people out of context can understand better
the forces in play here :)
- *Working directory and files constant property:* files defined using a
*relative path* are created relative to the working directory.
In other words:
File named:
Hi Stefan,
> Le 8 nov. 2017 à 15:56, stephan a écrit :
>
> I run into all kinds of issues with the directory structure used by the new
> PharoLauncher. pharo-local seems to be shared now for multiple images.
I never saw this issue.
PharoLauncher does not have influence on
I run into all kinds of issues with the directory structure used by the
new PharoLauncher. pharo-local seems to be shared now for multiple
images. That makes using configurations practically impossible as they
are not expecting to have to deal with pre-downloaded older and newer
monticello
10 matches
Mail list logo