Re: [Pharo-project] Method versioning in Pharo images

2009-11-30 Thread Mariano Martinez Peck
On Mon, Nov 30, 2009 at 12:31 PM, Michael Rueger wrote: > Stéphane Ducasse wrote: > > Michael > > > > do you have this code somewhere? > > Yes, need to package it up. > > It uses glorp and a postgres database as the backend. > > Like VW Store does, at least postgresql (I am not sure about Glorp)

Re: [Pharo-project] Method versioning in Pharo images

2009-11-30 Thread Michael Rueger
Stéphane Ducasse wrote: > Michael > > do you have this code somewhere? Yes, need to package it up. It uses glorp and a postgres database as the backend. Michael ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.in

Re: [Pharo-project] Method versioning in Pharo images

2009-11-30 Thread Stéphane Ducasse
Michael do you have this code somewhere? Because veronica will probably build something in that vein for her PhD on versioning. Stef On Nov 29, 2009, at 10:59 AM, Michael Rueger wrote: > Marcus Denker wrote: > >> What I would want to have is a server with all old code that than is >> queried

Re: [Pharo-project] Method versioning in Pharo images

2009-11-30 Thread Stéphane Ducasse
> We had to make new .sources for 1.0... and even if not: the problem is that > the .changes can only > be 32MB, and that is reached fast. In 3.9, we even had to condense changes in > the middle of the release cycle. > (This is what you get from never moving on from outdated technology) > >

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Lukas Renggli
; From: pharo-project-boun...@lists.gforge.inria.fr > [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Marcus > Denker > Sent: Sunday, November 29, 2009 12:18 PM > To: Pharo-project@lists.gforge.inria.fr > Subject: Re: [Pharo-project] Method versioning in Pharo imag

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Schwab,Wilhelm K
versioning in Pharo images On Nov 29, 2009, at 6:15 PM, Schwab,Wilhelm K wrote: > However, for "independent" read "redundant." Take away the redundancy, and > there is a single point of failure. That keeps surfacing as a good idea, and > I fear the backlash onc

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Marcus Denker
On Nov 29, 2009, at 6:27 PM, Michael Rueger wrote: > Marcus Denker wrote: >> On Nov 29, 2009, at 6:15 PM, Schwab,Wilhelm K wrote: >> >>> What is the source of the change log size limit? >>> >> >> 32MB. > > Would it be possible with the current compiled method format to make the > source poin

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Michael Rueger
Marcus Denker wrote: > On Nov 29, 2009, at 6:15 PM, Schwab,Wilhelm K wrote: > >> What is the source of the change log size limit? >> > > 32MB. Would it be possible with the current compiled method format to make the source pointer a first class object? A looong time ago I did that in VW and us

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Marcus Denker
On Nov 29, 2009, at 6:15 PM, Schwab,Wilhelm K wrote: > However, for "independent" read "redundant." Take away the redundancy, and > there is a single point of failure. That keeps surfacing as a good idea, and > I fear the backlash once the redundancy gets removed in the name of saving > spac

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Schwab,Wilhelm K
hange log size limit? -Original Message- From: pharo-project-boun...@lists.gforge.inria.fr [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Marcus Denker Sent: Sunday, November 29, 2009 8:55 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Method versioning

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Marcus Denker
gt; [mailto:pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Marcus > Denker > Sent: Sunday, November 29, 2009 3:26 AM > To: Pharo-project@lists.gforge.inria.fr > Subject: Re: [Pharo-project] Method versioning in Pharo images > > > On Nov 29, 2009, at 1:27 AM, csra...@bol.com.br wr

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Schwab,Wilhelm K
] On Behalf Of Marcus Denker Sent: Sunday, November 29, 2009 3:26 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Method versioning in Pharo images On Nov 29, 2009, at 1:27 AM, csra...@bol.com.br wrote: > >> What I would want to have is a server with all old code

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Michael Rueger
Marcus Denker wrote: > What I would want to have is a server with all old code that than is > queried by the image... Almost a year ago I did some work on a database, but then it got stuck on the back burner. What would be helpful in the future would be to have unique ids for every method, clas

Re: [Pharo-project] Method versioning in Pharo images

2009-11-29 Thread Marcus Denker
On Nov 29, 2009, at 1:27 AM, csra...@bol.com.br wrote: > >> What I would want to have is a server with all old code that than >> is queried by the image... > > Marcus, let me ask to put in this wish list we could have then a > versioning system similar to RCS/CVS and family where you

Re: [Pharo-project] Method versioning in Pharo images

2009-11-28 Thread csrabak
Em 28/11/2009 21:19, Marcus Denker < den...@acm.org > escreveu: > On Nov 28, 2009, at 9:42 PM, csra...@bol.com.br wrote: > > > I would like to know if the past history of the method's versions > >has been lost by design or accident. > > In the core image for example it is possible only for the

Re: [Pharo-project] Method versioning in Pharo images

2009-11-28 Thread Marcus Denker
On Nov 28, 2009, at 9:42 PM, csra...@bol.com.br wrote: > I would like to know if the past history of the method's versions has been > lost by design or accident. > > In the core image for example it is possible only for the method Object>>at: > an entry "yo 6/29/2004 11:39". > > Are we consid

[Pharo-project] Method versioning in Pharo images

2009-11-28 Thread csrabak
I would like to know if the past history of the method's versions has been lost by design or accident. In the core image for example it is possible only for the method Object>>at: an entry "yo 6/29/2004 11:39". Are we considering the implementation of Pharo as a clean slate and we'll start fro