Ahh tx I understand now.
I can tell you that I'm eager to do integration with git to avoid to
get MC checking all the repo from earth and merging :)
Stef
On Mon, Jun 19, 2017 at 1:09 PM, Peter Uhnak wrote:
> Hi,
>
> there was an issue with presumably gitfiletree, that when checking a code
> aga
Hi,
there was an issue with presumably gitfiletree, that when checking a code
against its repo (to commit or show changes), every single repository would be
refreshed, which took quite a while (on the order of seconds to tens of
seconds, but it was quite annoying as it happened frequently).. so
Well, that is the question to the author of original script - Peter Uhnak.
The goal is to avoid contacting server (takes alot of time and blocks the
image) every time you save a package to a filetree repo. As I understand
repositories in question are kind of special and are always checked, so
remo
Hi ww
Can you explain what your script do or even better what is the scenario ?
You remove all the pharo60 and 60 inbox from the packages. ok
This because you do not want to do merge? or changes comparison?
Tx for sharing it.
On Fri, Jun 16, 2017 at 2:43 PM, webwarrior wrote:
> Updated script
Updated script for Pharo6:
StartupPreferencesLoader default executeAtomicItems: {
StartupAction
name: 'remove references to Pharo60 and Pharo60Inbox'
code: [
|rx group|
rx := '([0-9]{5})' asRegex.
(rx matchesPrefix: Smalltalk image shortImageName) ifFalse:
As this is a real nuisance, I might have a partial solution — remove the
repos :)
Apart from contributing to pharo (which is done in clean images) I never
needed reference to those repositories, so I don't see why I would need
them there.
So a startup script to the rescue
StartupPreferencesLoade
On 6/3/16 2:43 AM, Otto Behrens wrote:
For FileTree repos it is even better to just load the package (Monticello
does a good job of only loading the changed packages and we're looking at
packages already on disk) ... ... I have an extension to Metacello for
Filetree repos (it's only been aroun
In the Monticello Browser, select the repository that you will be saving
your package to and use the "Flush cached versions" menu item ... it
seems that you have to do it before each package save...
Dale
On 6/3/16 12:13 AM, Peter Uhnak wrote:
On Wed, Jun 01, 2016 at 10:28:12PM -0700, Dale Hen
> For FileTree repos it is even better to just load the package (Monticello
> does a good job of only loading the changed packages and we're looking at
> packages already on disk) ... ... I have an extension to Metacello for
> Filetree repos (it's only been around for about 3 years) that ignores
>
On Wed, Jun 01, 2016 at 10:28:12PM -0700, Dale Henrichs wrote:
>
> FWIW, I've found that if I manually flush the cache for each package before
> I save it, I don't have to wait the minute or so for all of the repos to be
> refreshed ...
>
How can I do that?
Peter
On 5/29/16 5:28 AM, Thierry Goubier wrote:
Le 29/05/2016 14:04, Peter Uhnak a écrit :
On Sun, May 29, 2016 at 11:21:21AM +0200, Thierry Goubier wrote:
Le 29/05/2016 11:15, Peter Uhnák a écrit :
> All this is so that my .5 would not conflict with someone else .5
How is this a problem? Beca
I don't see anything actionable in this thread.
What can we do to move this forward? Is it only up to Dale to change the
behavior?
Can we have some workaround? E.g. syncing in the background at regular
intervals so when I want to commit I am not blocked by it?
Because it doesn't always check the
For some reason the package manager is refreshing all packages. I don't know
why it happens, and it's quite annoying (because it slows down commits), but it
doesn't cause any actual problems, so don't worry about it too much.
As I understand it, what happens is the following: before you commi
Le 29/05/2016 14:04, Peter Uhnak a écrit :
On Sun, May 29, 2016 at 11:21:21AM +0200, Thierry Goubier wrote:
Le 29/05/2016 11:15, Peter Uhnák a écrit :
> All this is so that my .5 would not conflict with someone else .5
How is this a problem? Because it will be "Me.5" and "You.5", so there
ca
On Sun, May 29, 2016 at 11:21:21AM +0200, Thierry Goubier wrote:
> Le 29/05/2016 11:15, Peter Uhnák a écrit :
> > > All this is so that my .5 would not conflict with someone else .5
> >
> > How is this a problem? Because it will be "Me.5" and "You.5", so there
> > can't be any conflict.
>
> Me.5
Le 29/05/2016 11:15, Peter Uhnák a écrit :
> All this is so that my .5 would not conflict with someone else .5
How is this a problem? Because it will be "Me.5" and "You.5", so there
can't be any conflict.
Me.5 and Me.5 are possible...
Think of numbering your own stuff on two different branch
> All this is so that my .5 would not conflict with someone else .5
How is this a problem? Because it will be "Me.5" and "You.5", so there
can't be any conflict.
Peter
On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe
wrote:
>
> > On 29 May 2016, at 10:28, Holger Freyther wrote:
> >
> >
> On 29 May 2016, at 10:28, Holger Freyther wrote:
>
>
>> On 29 May 2016, at 09:58, Sven Van Caekenberghe wrote:
>>
>>
>>>
>>> For some reason the package manager is refreshing all packages. I don't
>>> know why it happens, and it's quite annoying (because it slows down
>>> commits), but
> On 29 May 2016, at 09:58, Sven Van Caekenberghe wrote:
>
>
>>
>> For some reason the package manager is refreshing all packages. I don't know
>> why it happens, and it's quite annoying (because it slows down commits), but
>> it doesn't cause any actual problems, so don't worry about it too
> On 29 May 2016, at 09:51, Peter Uhnak wrote:
>
> On Sat, May 28, 2016 at 10:48:47PM +0200, Holger Freyther wrote:
>> Hi,
>>
>> every time I save a local package using gitfiletree:// it tries to download
>> from the pharo5 inbox. Is this to be expected? I do not have the inbox
>> associated
On Sat, May 28, 2016 at 10:48:47PM +0200, Holger Freyther wrote:
> Hi,
>
> every time I save a local package using gitfiletree:// it tries to download
> from the pharo5 inbox. Is this to be expected? I do not have the inbox
> associated with that package though? Can the version number resolving
21 matches
Mail list logo