Quantcast

filetree metadataless on Pharo 3.0?

Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

filetree metadataless on Pharo 3.0?

EstebanLM
Hi, 

for backward compatibility, I need to be able to use metadataless format on Pharo 3.0… and looks like this instructions (taken from README.md), do not work for it... 

Metacello new
  baseline: 'Metacello';
  repository: '<a href="github://dalehenrich/metacello-work:master/repository" class="">github://dalehenrich/metacello-work:master/repository';
  get.
Metacello new
  baseline: 'Metacello';
  repository: '<a href="github://dalehenrich/metacello-work:master/repository" class="">github://dalehenrich/metacello-work:master/repository';
  onConflict: [:ex | ex allow];
  load

is possible that metadataless is not ported to 3.0?
is possible to do it, in case it is not?

cheers, 
Esteban

--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: filetree metadataless on Pharo 3.0?

Dale Henrichs-3

What "doesn't work" with the Metacello load? It works for me and I'm running:

foos:tode>pharo-vm/pharo --version
3.9-7 #1 Thu May 15 18:29:30 CEST 2014 gcc 4.6.3 [Production ITHB VM]
NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 15 2014
NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 15 2014
https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano [hidden email] Jenkins build #14826
Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
plugin path: /export/foos1/users/dhenrich/dev/_home/dev/clients/tode/pharo-vm/ [default: /export/foos1/users/dhenrich/dev/_home/dev/clients/tode/pharo-vm/]

... I expect it to work on OSX as well, ... tODE runs in Pharo 3.0, and the latest Metacello is required there, so I'm a bit surprised that you are having trouble ...

If you are using Windows ... the you should use the dev_win-hack branch and cross your fingers...

I don't think that metadataless has been ported to Pharo3.0, but I also think that all versions of FileTree should read metadataless repositories ... although I haven't fiddled with FileTree for Pharo3.0 for a long time.

It looks like Thierry Goubier has done work as recent as October 2015[1] which may or may not include the metadataless support/ You might check with Thierry.

[1] https://github.com/dalehenrich/filetree/commits/pharo3.0
On 02/22/2017 05:37 AM, Esteban Lorenzano wrote:
Hi, 

for backward compatibility, I need to be able to use metadataless format on Pharo 3.0… and looks like this instructions (taken from README.md), do not work for it... 

Metacello new
  baseline: 'Metacello';
  repository: '<a moz-do-not-send="true" href="github://dalehenrich/metacello-work:master/repository" class="">github://dalehenrich/metacello-work:master/repository';
  get.
Metacello new
  baseline: 'Metacello';
  repository: '<a moz-do-not-send="true" href="github://dalehenrich/metacello-work:master/repository" class="">github://dalehenrich/metacello-work:master/repository';
  onConflict: [:ex | ex allow];
  load

is possible that metadataless is not ported to 3.0?
is possible to do it, in case it is not?

cheers, 
Esteban
--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Loading...