Issue 6064 in pharo: Could newer Zinc Version be included in Pharo 1.4 „Summer Edition“?

Status: New
Owner: ----
Labels: Milestone-1.4 Type-Feature

New issue 6064 by [hidden email]: Could newer Zinc Version be  
included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

I don’t know what’s the policy on this, but it would perhaps be nice if  
Zinc could be updated to newer Version/Configuration in Pharo 1.4 so one  
doesn’t have to do it manually..

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

Yes, that should be done.

I wanted to request another update around the time of the Pharo Conference.

But now, I would like to wait a bit and try to make a version that is  
compatible with the new FS stuff in 2.0. I have not yet looked at that, but  
it could be a bit of work to keep compatibility with 1.3 and 1.4 - which I  
definitively want.

I'll try to have a look at the changes needed for 2.0 FS this weekend.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Cc: [hidden email]

Comment #2 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

Should the latest FS just be included too? I say that because it seems FS  
wouldn't depend on anything else in the system... Is the API  
backward-compatible to 1.4? There may be just bug fixes, which we would  
want in 1.4.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

Well, I do have a (small) (source code management) problem: in order to  
support Zn for 1.3, 1.4 *and* 2.0 some file operation dependent code will  
(have to) be different. I don't want to include an abstraction layer. So I  
was thinking about an ugly override package (if that even works OK). You  
suggestion is another idea, yes. But I believe the standalone FS is not  
that well supported, is it ? I would need it in 1.3 and 1.4.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Accepted
        Labels: -Type-Feature Type-Enh

Comment #4 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

I was thinking that we could make a repo called e.g. PharoFileSystem and  
mirror/host the packages from 2.0 there. Then we could load it in 1.3, 1.4,  
or wherever; and version it with Metacello. This is based on the assumption  
that FS will not depend on [much|anything] else in 2.0 because it's so  
foundational. This seems like a reasonable assumption and was confirmed by  
Cami.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Cc: [hidden email]

Comment #5 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

(No comment was entered for this change.)

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #6 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

The code split for Zn pre/post the introduction of FileSystem in 2.0 has  
been done.
The new code is now in 2.0 and working.
Sean did a new Metacello configuration (unpublished for now).

Here is an old fashion load script:

Gofer it
   url: 'http://mc.stfx.eu/ZincHTTPComponents';
   package: 'Zinc-HTTP';
   package: 'Zinc-Tests';
   package: 'Zinc-FileSystem-Legacy';
   load.

You have to do a recompileAll afterwards.

BTW this update is urgently needed because a lot of tests were using  
mac.com URLs that are now dead (well, they redirect to HTTPS ;-)

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #7 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

sven's script will be the easiest way...
And, the new config has been uploaded to sqs/MetacelloRepository &  
sqs/ZincHTTPComponents

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixToInclude

Comment #8 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

(No comment was entered for this change.)

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Integrated

Comment #9 on issue 6064 by [hidden email]: Could newer Zinc Version  
be included in Pharo 1.4 „Summer Edition“?
http://code.google.com/p/pharo/issues/detail?id=6064

in 14450

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker