[Pharo-users] Package Install problematic
Ciao, after a Pharo 7.0 - 64 bit crash, for now irrecoverable, where i lose some works. ( i'm not happy for some days ). I'm trying to set up a new image. But. Because i think to messed up on /home/party/Pharo/images/Pharo 7.0 - 64bit (development version) i rename it. After with the command: wget -O- https://get.pharo.org/64/70+vm | bash i create new lonely /opt/pharo7.0.0rc1b57 build 57 image With this command the system create a new directory: /home/party/Pharo/images/Pharo 7.0 - 64bit (development version) Into Iceberg i import my local existing entry repository: Seaside master 9566cb4 add MetacelloAllowLockedProjectChange handling When on this repository i do the Metacello Install baseline of Seaside3 (default) the system open a Window with titled: Could not resolve: ConfigurationOfZincHTTPComponents [ConfigurationOfZincHTTPComponents] in /home/party/Pharo/images/Pharo 7.0 - 64bit (development version)/pharo-local/package-cache http://mc.stfx.eu/ZincHTTPComponents The Metacello report a package entry with: BaselineOfSeaside3 (CompatibleUserName.1537724254) with repository set to: /home/party/Pharo/images/Pharo 7.0 - 64bit (development version)/pharo-local/package-cache Why this situation? Considerations? Thanks, Dario
Re: [Pharo-users] Pharo stable version with git support
Ciao, thanks. > Hi Dario, >> i'm interested to port all my code to new Pharo version that manage >> git support. >> >> I found information in pharo.org news, it talk of Pharo 6.1. >> >> But it run only on macOS 64bits o i can run it on Linux Ubuntu 16.04 >> LTS System? >> >> New information - update about it? >> > > Pharo 6.1 runs on 64bits, except for windows. > > OK, i have setup a Pharo 6.1 image with Iceberg update as > https://github.com/pharo-vcs/iceberg > > Now i'm "new" to git support .. > > Take into account that this is highly necessary. The version of Iceberg in > Pharo 6.1 is just an old preview version. > While Pharo works on 64 bits, Iceberg itself was not at that time, so > upgrading is necessary to have that support. 1) OK, i have do the upgrade to: iceberg:dev-0.7 "load iceberg" Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:v1.?'; onWarningLog; load. "Re-initialize libgit2" (Smalltalk at: #LGitLibrary) initialize. But it's the last version ? How i can understand what is the right version to update ? 2) for error i delete the..shared/pharo-local/iceber/git/iceberg directory. i need to setup a new pharo environment ? > > > I understand ???that Iceberg has some limitations, it is not > complete .. > > Iceberg already has pretty good support to manage pharo code. > > You'll find however that it does not manage (yet) non-pharo files. That is, > if your repository has scripts, pictures or such kind of resources, you will > have for now to edit and commit them from the outside (command line or > another tool). > > The reasons for that are so far explained in here > https://github.com/pharo-vcs/iceberg/blob/master/docs/The-Working-Copy(ies).md > > I would be grateful if someone explained to me how operatively I can > manage everything ... > > up to where I can do with Iceberg directly from Pharo and how to > operate from the shell on the git repository. > > Documentation in this sense? > > Well, you have iceberg's wiki > > https://github.com/pharo-vcs/iceberg/wiki > > We are moving the documentation (hey, bit thanks to Tim Mackinon here!) to > the main repository so people can easy contribute to it. > See https://github.com/pharo-vcs/iceberg/tree/master/docs. > What is left is a sync mechanism between that directory and the wiki > repository. > > My goal is to setup a environment for integrate Pharo development with > Gemstone GLASS Tode git support. > > Does anyone have experience in this sense? > > That's not me, I hope you'll find somebody. But if you have any questions > regarding Iceberg, don't hesitate to ask them! You intend at this support ? Thanks, Dario
Re: [Pharo-users] Pharo stable version with git support
Ciao, > > > On 2 July 2018 at 23:32, dario.trussa...@tiscali.it > wrote: > Ciao, > > i'm interested to port all my code to new Pharo version that manage > git support. > > I found information in pharo.org news, it talk of Pharo 6.1. > > But it run only on macOS 64bits o i can run it on Linux Ubuntu 16.04 > LTS System? > > New information - update about it? > > Thank you for every consideration, > > Dario > > > At http://pharo.org/download you can either: > 1. At top of page click the "GNU/Linux" to install 64-bit PharoLauncher. > This gives you manage multiple 64bit or 32bit images > although the latter requires some i386 dependencies to be manually > installed. > > 2. Further down click "Pharo 6.1 for GNU/Linux (64bit)" >which provides a single installation you can unzip where you like. > > cheers -ben Thanks, OK, i have setup a Pharo 6.1 image with Iceberg update as https://github.com/pharo-vcs/iceberg Now i'm "new" to git support .. I understand ???that Iceberg has some limitations, it is not complete .. I would be grateful if someone explained to me how operatively I can manage everything ... up to where I can do with Iceberg directly from Pharo and how to operate from the shell on the git repository. Documentation in this sense? My goal is to setup a environment for integrate Pharo development with Gemstone GLASS Tode git support. Does anyone have experience in this sense? Thanks, Dario
Re: [Pharo-users] Code porting to Pharo 6.1-64
I wrong... the error is relative to my root class ... For this class i implemented the class method propertyAt: aKey ifAbsent: aBlock This is in conflict with : the Behavior originalName method implement: ^ (( self isObsolete and:[ self name beginsWith: 'AnObsolete whereisObsolete TClass is: self propertyAt: #obsolete ifAbsent: false Thanks for considerations, Dario > Ciao, > > i work to port some code from Pharo 4.0 to Pharo 6.1-64. > > My root class into Pharo 4.0 define the properties > > instance variable and some relative method: > > a) propertyAt: aKey ifAbsent: aBlock > > ^ self properties at: aKey ifAbsent: > aBlock > > b) propertyAt: aKey ifAbsentPut: aBlock > > ^ self properties at: aKey ifAbsentPut: > aBlock > > c) propertyAt: aKey put: aValue > > ^ self properties at: aKey put: aValue > > d).. > > Now when i port this code into the Pharo 6.1-64 when compile the code > > the Behavior originalName method implement: > > ^ (( self isObsolete and:[ self name beginsWith: > 'AnObsolete > > > whereisObsolete TClass is: > > self propertyAt: #obsolete ifAbsent: false > > > But my class implement a specificpropertyAt: > ifAbsent: method > > and the system generates errors and don't compile the code. > > > Thank you for every consideration. > > Dario > > > >
[Pharo-users] Code porting to Pharo 6.1-64
Ciao, i work to port some code from Pharo 4.0 to Pharo 6.1-64. My root class into Pharo 4.0 define the properties instance variable and some relative method: a) propertyAt: aKey ifAbsent: aBlock ^ self properties at: aKey ifAbsent: aBlock b) propertyAt: aKey ifAbsentPut: aBlock ^ self properties at: aKey ifAbsentPut: aBlock c) propertyAt: aKey put: aValue ^ self properties at: aKey put: aValue d).. Now when i port this code into the Pharo 6.1-64 when compile the code the Behavior originalName method implement: ^ (( self isObsolete and:[ self name beginsWith: 'AnObsolete whereisObsolete TClass is: self propertyAt: #obsolete ifAbsent: false But my class implement a specificpropertyAt: ifAbsent: method and the system generates errors and don't compile the code. Thank you for every consideration. Dario
[Pharo-users] Pharo stable version with git support
Ciao, i'm interested to port all my code to new Pharo version that manage git support. I found information in pharo.org news, it talk of Pharo 6.1. But it run only on macOS 64bits o i can run it on Linux Ubuntu 16.04 LTS System? New information - update about it? Thank you for every consideration, Dario
[Pharo-users] Error loading Seaside Gettext support
Ciao, i load correctly the Gettext support into: Pharo 6.1-64 Latest update: #60510 In the image was load the Seaside 3.2 Now i do: (ConfigurationOfSeaside3 project version: #stable ) load: #( 'Seaside-Gettext-Core' 'Seaside-Gettext-Examples'). The system erase the error: NaturalLanguageTranslator class(Object)>>doesNotUnderstand: #domainRegistered: TextDomainManager class>>registerDomain: [ self registerDomain: domainName ] in TextDomainManager class>>domainInfoFor: in Block: [ self registerDomain: domainName ] [ self at: key put: aBlock value ] in Dictionary>>at:ifAbsentPut: in Block: [ self at: key put: aBlock value ] Dictionary>>at:ifAbsent: Dictionary>>at:ifAbsentPut: TextDomainManager class>>domainInfoFor: TextDomainManager class>>registerCategoryPrefix:domain: WAGettextExample class>>register WAGettextExample class>>initialize Some considerations ? Thanks, Dario
