Hi--another question, this time on loading an external package into Pharo.
I want to do some work manipulating text, so I thought I would start by reading
the source code for an existing package that works on text.
Here's what I did:
On smalltalkhub.com, I found a package called Citezen, from
Hi,
I have a Pharo 6.1 image with packages loaded manually (without
BaselineOf or ConfigurationOf). Now if I evaluate a Metacello script
which would install the package already installed in the image (for
example via dependency), is there any check performed against the
RPackages or similar to
Hi guys,
I am working on Pharo 6.1 and already have an image with multiple
packages loaded via Iceberg. Every time I want to load other's remote
changes to my image I have to open the Iceberg UI and select
repository, synchronize, update, hit fetch + merge (or pull).
Does anyone has a script to
Tim and Ben,
Thanks for your help. Sorry for not being clear. When I said "I just can't get
keyboard shortcuts to work on Mac," what I should have said is "I just can't
get Pharo-specific shortcuts to work on the Macintosh implementation of Pharo"
(6.1 is what I'm using BTW).
Maybe I should
On 5 June 2018 at 00:59, Tim Mackinnon wrote:
> > P7 will force you to be in the right branch or you will not be able to
> do… almost anything :)
> > you can have two (or ten) images opened at once and work on them, but at
> a moment you will need to “repair” each image to commit.
>
> So are we
> On 4 Jun 2018, at 18:59, Tim Mackinnon wrote:
>
>> P7 will force you to be in the right branch or you will not be able to do…
>> almost anything :)
>> you can have two (or ten) images opened at once and work on them, but at a
>> moment you will need to “repair” each image to commit.
>
>
> but I’m trying to understand what is the easiest option to avoid
gotcha’s (that more advanced guys can better cope with)
I guess the question is whether you want to handle conflict resolutions
directly with git, or through iceberg.
I've been using separate clones for each image for a long
Esteban Lorenzano
wrote:
.
> P7 will force you to be in the right branch or you will not be able to
> do… almost anything :)
> you can have two (or ten) images opened at once and work on them, but at
> a moment you will need to “repair” each image to commit.
Ah, nice. How is that guarded
> P7 will force you to be in the right branch or you will not be able to do…
> almost anything :)
> you can have two (or ten) images opened at once and work on them, but at a
> moment you will need to “repair” each image to commit.
So are we saying that the easiest and less complicated option
hi,
> On 4 Jun 2018, at 12:57, Stephan Eggermont wrote:
>
> Evan Donahue wrote:
>> I have "Share repositories between images" checked in both images,
>
> Share repositories at the moment just provides a shared location on disk
> where the repositories are located. That is only useful if you
Evan Donahue wrote:
> I have "Share repositories between images" checked in both images,
Share repositories at the moment just provides a shared location on disk
where the repositories are located. That is only useful if you are very
disciplined about stashing and switching to the branch needed
2018-06-04 10:42 GMT+02:00 Cyril Ferlicot D. :
> On 03/06/2018 16:42, Tudor Girba wrote:
>> Hi,
>>
>
> Hi,
>
>> I am working with a GitHub enterprise installation that resides under a
>> custom domain (e.g., github.example.com).
>>
>> I can clone the repository using Iceberg and ssh:
>>
On 03/06/2018 16:42, Tudor Girba wrote:
> Hi,
>
Hi,
> I am working with a GitHub enterprise installation that resides under a
> custom domain (e.g., github.example.com).
>
> I can clone the repository using Iceberg and ssh:
> g...@github.example.com:user/repo.git
>
> How can I tell
we have a problem with the automatic restart script: it restarts the server
regularly (‘rejuvenation' ;-)
But it fails restart if the process is not running at all.
to be fixed.
> On 3 Jun 2018, at 20:37, Bruce O'Neel wrote:
>
> Yep, seems fine now. Thanks!
>
> cheers
>
> bruce
>
> 03
14 matches
Mail list logo