- Pharo-users - lists.pharo.org

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Peter Uhnak

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 and Me.5 are possible... > > Think of numbering your own stuff on two different branches. > > More, Metacello depends on Me.5 5 to be greater than You.5 5 for some of the > baselines / configurations to work properly :) Can't it use the ancestry to decide? Because my impression is from this that merges are naive, compared to git which actually checks the ancestry of both up the common endpoint and diffs based on that. Peter > > Thierry > > > > > Peter > > > > On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe <sven(a)stfx.eu > > <mailto:sven@stfx.eu>> wrote: > > > > > > > On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de <mailto:holger@freyther.de>> wrote: > > > > > > > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> 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 much. > > >> > > >> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. > > > > > > I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) > > > > We should go one step further: add an option to totally disable this > > check to go outside the target repo, it makes little sense. But MC > > is a complex beast ... > > > > > holger > > > > > > > >

May 29, 2016

QCMagritte & Voyage?

by Udo Schneider

All, I'm currently trying to wrap my head around QCMagritte. So far it seems to include most of what I need. I'm not sure though how/where to integrate a persistency layer (i.e. Voyage in this case). I'm either missing some place to activly take control and do saving/upgrading or any callback when objects/collections have been changed. Any pointers or sample code? Thanks, Udo

May 29, 2016

Re: [Pharo-users] (no subject)

by frankl1_miky

Thanks for all your answers, It's true that pharo community is active. I'll give you feedback about my progress. I'm having fun with Pharo Mooc at this period. Thanks for your help! -- View this message in context: http://forum.world.st/no-subject-tp4894192p4897990.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Thierry Goubier

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 branches. More, Metacello depends on Me.5 5 to be greater than You.5 5 for some of the baselines / configurations to work properly :) Thierry > > Peter > > On Sun, May 29, 2016 at 10:37 AM, Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>> wrote: > > > > On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de <mailto:holger@freyther.de>> wrote: > > > > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> 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 much. > >> > >> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. > > > > I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) > > We should go one step further: add an option to totally disable this > check to go outside the target repo, it makes little sense. But MC > is a complex beast ... > > > holger > > >

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Peter UhnÃ¡k

> 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 <sven(a)stfx.eu> wrote: > > > On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de> wrote: > > > > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu> 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 much. > >> > >> As I understand it, what happens is the following: before you commit to > your MC repo, you have to find the next version number; a check is then > done in all relevant repos; the cached content is not used, but an actual > refresh is done. All this is so that my .5 would not conflict with someone > else .5 - the chance that this happens is very small, and the check does > not really prevent it. > > > > I assumed that but can it be limited to the Repositories that are > associated with the package? I am afraid that next time I travel I can not > commit to my local repository (and ofcourse the speed part). :) > > We should go one step further: add an option to totally disable this check > to go outside the target repo, it makes little sense. But MC is a complex > beast ... > > > holger > > >

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Sven Van Caekenberghe

> On 29 May 2016, at 10:28, Holger Freyther <holger(a)freyther.de> wrote: > > >> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu> 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 much. >> >> As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. > > I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) We should go one step further: add an option to totally disable this check to go outside the target repo, it makes little sense. But MC is a complex beast ... > holger

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Holger Freyther

> On 29 May 2016, at 09:58, Sven Van Caekenberghe <sven(a)stfx.eu> 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 much. > > As I understand it, what happens is the following: before you commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. I assumed that but can it be limited to the Repositories that are associated with the package? I am afraid that next time I travel I can not commit to my local repository (and ofcourse the speed part). :) holger

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Sven Van Caekenberghe

> On 29 May 2016, at 09:51, Peter Uhnak <i.uhnak(a)gmail.com> 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 with that package though? Can the version number resolving be changed? > > 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 commit to your MC repo, you have to find the next version number; a check is then done in all relevant repos; the cached content is not used, but an actual refresh is done. All this is so that my .5 would not conflict with someone else .5 - the chance that this happens is very small, and the check does not really prevent it. > Peter > >> >> kind regards >> holger >

May 29, 2016

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Peter Uhnak

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 be changed? 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. Peter > > kind regards > holger

May 29, 2016

Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Holger Freyther

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 be changed? kind regards holger

May 28, 2016