About store

Some old versions of RB are published in our store :( (in fact only  
one version)

Now each time I load code that rely on more recent versions, my  
system is fucked up.

I marked these packages as broken
but even if I set up
        - load latest version
        >> with blessing level at least dev
        - search bundle first

this wonderful store loads them. So is there something that we can do.

Stef

Well, my guess would be that it's not Store that's loading them, but that you're finding something from parcels on the disk. I load code from a repository that has every old version of the RB and along with every other old component and don't run into a problem.

However, it would probably be helpful if you provided slightly more information. For example, if you tell it to always prompt for version, is it prompting you for a version of the RB? My second guess would probably be that some component explicitly specifies a version of a prerequisite. My third would be that some components have been renamed, and the latest version under the name that's being searched for is the old one (or something that explicitly prereqs the old version). Fourth would be that the old version has a more recent timestamp in the database, but that seems contradicted by the selecting blessing level.

Since you have an environment with interesting reflective capabilities, you might try putting a breakpoint in Store loading (or even just hit ctrl-y while it's loading). I suspect that StoreBundle>>dbLoadWithin: might be a good spot, or possibly loadSrcWithImgPundle:. That would probably give you a good indicator of how it got to loading a particular version, or at least give you a stack trace that might be more informative.

At 03:43 PM 9/27/2006, stéphane ducasse wrote:
--
Alan Knight [|], Cincom Smalltalk Development
[hidden email]
[hidden email]
http://www.cincom.com/smalltalk

"The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross

hi Alan

I'm writing a loader in the hope that I will be able to specify  
exactly which versions should be loaded from where.

> Well, my guess would be that it's not Store that's loading them,  
> but that you're finding something from parcels on the disk.

Do you imply that a parcel prerequisites could load a store packages  
(even with the set up I said). Normally I have the latest  
distribution 7.4.1 so I was thinking that a parcel would load another  
parcel or follow the advice given to load store elements.

> I load code from a repository that has every old version of the RB  
> and along with every other old component and don't run into a problem.

For me as soon as I put load latest, I get a broken editor. I cannot  
browse code anymore. So this is not fun.

>
> However, it would probably be helpful if you provided slightly more  
> information. For example, if you tell it to always prompt for  
> version, is it prompting you for a version of the RB? My second  
> guess would probably be that some component explicitly specifies a  
> version of a prerequisite. My third would be that some components  
> have been renamed,

Yes I have the impression

> and the latest version under the name that's being searched for is  
> the old one (or something that explicitly prereqs the old version).

But in the first place I do not understand why this store element is  
loaded. This means that may be I have another epackage that hardcode  
a dependency to a broken element. But if I start without load package  
first then everything works well. So I have the impression that store  
is still not acting well.
Because
        imagine PA ask to load PB (borken on store) PB (working on parcel)
        it works well I check first parcels
        it breaks when I check with package (so the setting are not checked  
correctly or I do a mistake).

> Fourth would be that the old version has a more recent timestamp in  
> the database, but that seems contradicted by the selecting blessing  
> level.

In the DB there is only one version of the broken component.
>
> Since you have an environment with interesting reflective  
> capabilities, you might try putting a breakpoint in Store loading  
> (or even just hit ctrl-y while it's loading). I suspect that  
> StoreBundle>>dbLoadWithin: might be a good spot, or possibly  
> loadSrcWithImgPundle:. That would probably give you a good  
> indicator of how it got to loading a particular version, or at  
> least give you a stack trace that might be more informative.

Ok I will look the problem is that this is one shot debugging after  
my image is screwed and my network is slow.

Missing copy and paste is sooooooo frustrating on mac. You PC people  
cannot realize
how terrible it is to program on VW on mac. I hope to be able to get  
my hands on a
VM that works for mac one of these days. But I'm losing so much time  
with that.

To the point that we should better give PC to new guys coming to  
smalltalk. Terrible that too.

I cannot copy you the log
but it say

Autoloading RBBrowserUI from /obsolote/parcels/RBbrowserUI
RBBrowserUI has been renamed to Browser-BrowserUI

So I will try to understand what I can do.......
beside sleeping now.

Stef

At 04:45 PM 9/27/2006, stéphane ducasse wrote:
OK, that sounds extremely likely to be the cause. So my guess is that in the parcel versions shipped with the product, the broken component is not listed in prerequisites. However, in the latest versions in your repository, one of them references the broken component. I would turn on the facility to ask it which version to load. When it asks you to load the broken component, hit control-Y and then scroll back in the debugger to see which package it was processing prerequisites for when it asked this.


--
Alan Knight [|], Cincom Smalltalk Development
[hidden email]
[hidden email]
http://www.cincom.com/smalltalk

"The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross

Cut and paste works, it's just mapped to the wrong keys. Using ctrl-C rather than apple-C works, as does using Copy from the menu. And you PC people should be able to figure that out.

At 04:55 PM 9/27/2006, stéphane ducasse wrote:
--
Alan Knight [|], Cincom Smalltalk Development
[hidden email]
[hidden email]
http://www.cincom.com/smalltalk

"The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross

On 27 sept. 06, at 23:04, Alan Knight wrote:

> Cut and paste works, it's just mapped to the wrong keys. Using ctrl-
> C rather than apple-C works, as does using Copy from the menu. And  
> you PC people should be able to figure that out.

Sorry alan but I know that and it does not work on mac
with other tools. There is no way that I can copy and paste from VW  
in my email.
I tried to change the preference of X11 and loaded the parcels of  
mircea to improve the situation but it does not work
reliability. It works the first time sometimes.

Stef

At 05:08 PM 9/27/2006, stéphane ducasse wrote:

Ah, I don't use the X11 VM.
--
Alan Knight [|], Cincom Smalltalk Development
[hidden email]
[hidden email]
http://www.cincom.com/smalltalk

"The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross

stéphane ducasse wrote: Ahh.. This is something I can actually answer!  I regularly use the X11
VW (under Linux) across an ssh connection
to my Macintosh..  Anyway, here's what you do -- and yes it is a bit
convoluted!  First -- select the "stuff" to
be copied inside the VW window of interest.. Once it's copied either
using CTRL-C  or the Edit Menu, then go under the Mac's
X11 menu at the very top of the screen and select "Edit->Copy".. Once
you do that, your selected text will be on the regular old
Macintosh clipboard ready for pasting in any old Mac app.. Why Apples'
X11 emulation doesn't do this normally is beyond me!

For more info on this I ran across this -- doesn't solve the issue, but
others have seen it as well..

http://schwern.hates-software.com/2004/12/14/ecbfffd4.html

Wow! You really made my day with this information.

And now that I am rereading this email again, I realize I must be  
very much in love with Smalltalk to actually be happy that this works  
somehow :).

Cheers,
Tudor

On Sep 27, 2006, at 11:42 PM, Rick Flower wrote:

--
Tudor Adrian Girba                      Software Composition Group
(www.iam.unibe.ch/~girba)        University of Bern, Switzerland

"One cannot do more than one can do."

Tudor Girba wrote:
> Wow! You really made my day with this information.
>
> And now that I am rereading this email again, I realize I must be very
> much in love with Smalltalk to actually be happy that this works
> somehow :).
>
Glad I could help someone.. I stumbled across that by sheer stupidity..
Perhaps that sort of thing can be fixed some day by Apple..

At 06:55 PM 9/27/2006, Rick Flower wrote:
>Tudor Girba wrote:
>>Wow! You really made my day with this information.
>>
>>And now that I am rereading this email again, I realize I must be very much in love with Smalltalk to actually be happy that this works somehow :).
>Glad I could help someone.. I stumbled across that by sheer stupidity.. Perhaps that sort of thing can be fixed some day by Apple..

I suspect it's due to the difference between X's clipboard model and Apple's. X has a couple of different clipboards, but one common one is not so much cut and paste as select something and it automatically goes into the buffer. Mac users would probably be very confused if their clipboard kept getting replaced by whatever they selected in an X application.

--
Alan Knight [|], Cincom Smalltalk Development
[hidden email]
[hidden email]
http://www.cincom.com/smalltalk

"The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross

On 27 sept. 06, at 23:53, Tudor Girba wrote:

> Wow! You really made my day with this information.
>
> And now that I am rereading this email again, I realize I must be  
> very much in love with Smalltalk to actually be happy that this  
> works somehow :).

yes doru (fascinating).
imagine that you recame from IDEA and java now :).

A big love affair