0.15.0-pre
Locked
 
|
A Linux user should know this, but the export statement should be placed in ~/.bashrc for Terminal usage. (I'm a very occasional Linux user and I always forget this.)
-- On Monday, 18 May 2015 19:09:59 UTC-4, Richard Eng wrote:
You received this message because you are subscribed to the Google Groups "amber-lang" 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. |
|
|
In reply to this post by horrido
On 5/18/15, Richard Eng <[hidden email]> wrote:
> Hooray! It works! SUCCESS! Yes, now may I ask you to write a short test report 'Installation on OS X and Linux Mint' which is referred to from https://github.com/amber-smalltalk/amber/wiki/Getting-started ? And a suggestion for a next challenge is to set up an Amber environment which allows you to contribute to the development of Amber. Instructions are here https://github.com/amber-smalltalk/amber/blob/master/CONTRIBUTING.md You might join my efforts here Stuck at step 7 https://gitter.im/amber-smalltalk/amber An example of a simple contribution to Amber for example could be the addition of a method #perform:with: Amber only has #perform:withArguments But Pharo has as well #perform:with: --Hannes > > Too bad this procedure can't be simplified. A "one-step install" for Amber > would be soooo attractive and compelling. > > Thanks. > > > On Monday, 18 May 2015 19:09:59 UTC-4, Richard Eng wrote: >> >> LXLE didn't pan out; it's a rather unreliable distro. So I created a *new* >> >> Linux Mint VM (pristine install)... >> >> First, I had to install curl: >> >> sudo apt-get install curl >> >> Then, following the instructions here >> <https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories> >> : >> >> curl -sL https://deb.nodesource.com/setup_0.12 | sudo bash - >> >> sudo apt-get install -y nodejs >> >> I got Node 0.12.3. >> >> Then I installed Git: >> >> sudo apt-get install git >> >> Now to install Amber... >> >> npm config set prefix=~/npm >> >> export PATH="$PATH:$HOME/npm/bin" >> >> npm install -g amber-cli bower grunt-cli >> >> Now, 'amber init' does what it's supposed to do and the welcome app >> works! >> >> Whew! >> >> >> So you're right. It's all about *ownership*. Now, to try it in my OS X >> machine... >> >> >> On Monday, 18 May 2015 18:04:53 UTC-4, MKroehnert wrote: >> >> Dear Richard, >> >> you are facing the issue that the directory /Users/richardeng/.npm/ >> contains >> subdirectories which are not owned by your current user. >> You can check this with ls -l /Users/richardeng/.npm/ and most likely you >> >> will find some directories owned by root instead of richardeng. >> >> The cause for this is that earlier on you most probably installed some >> packages globally with sudo npm install -g which runs npm as root user. >> In this case you will not face issues immediately but only after a while >> when npm (run as regular user) tries to update package dependencies that >> have previously been installed with sudo npm. >> >> One way around this is to change the owner of everything inside >> /Users/richardeng/.npm/ to richardeng and the usergroup. >> >> But as it was already mentioned, it would be much better to delete the >> /Users/richardeng/.npm/ directory completely and follow the advice from >> the Amber getting started guide (the one which does not require using sudo >> >> npm). >> >> Best, >> Manfred >> >> >> >> >> On Mon, May 18, 2015 at 7:59 PM, Richard Eng <[hidden email]> >> wrote: >> >> 'amber init' seems to generate a lot of error messages... >> >> *Initialized from template "grunt-init-amber".* >> >> You need to have these installed globally via npm: amber-cli_; >> _grunt-cli_; >> >> _bower. Now, install project dependencies with bower install, tool >> >> dependencies with npm install and optionally, recompile with grunt. If >> you >> >> are running amber init, these three tasks are going to be performed for >> you >> >> now. Afterwards, start the development server with amber serve. Your >> >> application is then accessible via http://localhost:4000/ >> >> >> Done, without errors. >> >> bower cached git://github.com/amber-smalltalk/helios.git#0.4.3 >> >> bower validate 0.4.3 against git:// >> github.com/amber-smalltalk/helios.git#^0.4.0 >> >> bower cached git:// >> github.com/amber-smalltalk/amber-contrib-legacy.git#0.2.0 >> >> bower validate 0.2.0 against git:// >> github.com/amber-smalltalk/amber-contrib-legacy.git#^0.2.0 >> >> bower cached git://github.com/amber-smalltalk/amber.git#0.14.13 >> >> bower validate 0.14.13 against git:// >> github.com/amber-smalltalk/amber.git#^0.14.13 >> >> bower cached git:// >> github.com/amber-smalltalk/amber-ide-starter.git#0.1.0 >> >> bower validate 0.1.0 against git:// >> github.com/amber-smalltalk/amber-ide-starter.git#^0.1.0 >> >> bower cached git://github.com/amber-smalltalk/amber.git#0.14.13 >> >> bower validate 0.14.13 against git:// >> github.com/amber-smalltalk/amber.git#>=0.14.13 >> >> bower cached git://github.com/jquery/jquery.git#2.1.4 >> >> bower validate 2.1.4 against git://github.com/jquery/jquery.git# >> >=1.7.0 >> >> bower cached git://github.com/components/jqueryui.git#1.11.4 >> >> bower validate 1.11.4 against git:// >> github.com/components/jqueryui.git#>=1.9.2 >> >> bower cached git://github.com/ccampbell/mousetrap.git#1.5.2 >> >> bower validate 1.5.2 against git:// >> github.com/ccampbell/mousetrap.git#^1.4.6 >> >> bower cached git://github.com/guybedford/require-css.git#0.1.8 >> >> bower validate 0.1.8 against git:// >> github.com/guybedford/require-css.git#^0.1.2 >> >> bower cached git://github.com/showdownjs/showdown.git#0.3.4 >> >> bower validate 0.3.4 against git:// >> github.com/showdownjs/showdown.git#^0.3.1 >> >> bower cached git:// >> github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#2.3.2 >> >> bower validate 2.3.2 against git:// >> github.com/alonisser/bower-bootstrap-2.3.2-legacy.git#^2.3.2 >> >> bower cached git://github.com/malsup/blockui.git#2.65 >> >> bower validate 2.65 against git://github.com/malsup/blockui.git#2.65 >> >> bower cached git://github.com/marijnh/CodeMirror.git#4.13.0 >> >> bower validate 4.13.0 against git:// >> github.com/marijnh/CodeMirror.git#^4.7.0 >> >> bower cached git://github.com/jquery/jquery.git#2.1.4 >> >> bower validate 2.1.4 against >> git://github.com/jquery/jquery.git#>=1.6 >> >> bower cached git://github.com/jquery/jquery.git#2.0.3 >> >> bower validate 2.0.3 against >> git://github.com/jquery/jquery.git#>=1.8.0 >> <2.1.0 >> >> bower cached git://github.com/jquery/jquery.git#2.1.4 >> >> bower validate 2.1.4 against >> git://github.com/jquery/jquery.git#>=1.7 >> >> bower install amber-ide-starter-dialog#0.1.0 >> >> bower install helios#0.4.3 >> >> bower install amber-contrib-legacy#0.2.0 >> >> bower install amber#0.14.13 >> >> bower install jquery-ui#1.11.4 >> >> bower install require-css#0.1.8 >> >> bower install mousetrap#1.5.2 >> >> bower install showdown#0.3.4 >> >> bower install bootstrap2.3.2#2.3.2 >> >> bower install blockui#2.65 >> >> bower install jquery#2.0.3 >> >> bower install codemirror#4.13.0 >> >> >> amber-ide-starter-dialog#0.1.0 bower_components/amber-ide-starter-dialog >> >> ├── blockui#2.65 >> >> └── mousetrap#1.5.2 >> >> >> helios#0.4.3 bower_components/helios >> >> ├── amber#0.14.13 >> >> ├── bootstrap2.3.2#2.3.2 >> >> ├── codemirror#4.13.0 >> >> ├── jquery#2.0.3 >> >> ├── jquery-ui#1.11.4 >> >> ├── require-css#0.1.8 >> >> └── showdown#0.3.4 >> >> >> amber-contrib-legacy#0.2.0 bower_components/amber-contrib-legacy >> >> ├── amber#0.14.13 >> >> ├── codemirror#4.13.0 >> >> ├── jquery-ui#1.11.4 >> >> └── require-css#0.1.8 >> >> >> amber#0.14.13 bower_components/amber >> >> └── jquery#2.0.3 >> >> >> jquery-ui#1.11.4 bower_components/jquery-ui >> >> └── jquery#2.0.3 >> >> >> require-css#0.1.8 bower_components/require-css >> >> >> mousetrap#1.5.2 bower_components/mousetrap >> >> >> showdown#0.3.4 bower_components/showdown >> >> >> bootstrap2.3.2#2.3.2 bower_components/bootstrap2.3.2 >> >> └── jquery#2.0.3 >> >> >> blockui#2.65 bower_components/blockui >> >> └── jquery#2.0.3 >> >> >> jquery#2.0.3 bower_components/jquery >> >> >> codemirror#4.13.0 bower_components/codemirror >> >> npm install exec error: >> >> { [Error: Command failed: /bin/sh -c npm install >> >> npm WARN locking Error: EACCES, open >> '/Users/richardeng/.npm/_locks/grunt-contrib-requirejs-38a39c12cfe7332d.lock' >> >> npm WARN locking at Error (native) >> >> npm WARN locking >> /Users/richardeng/.npm/_locks/grunt-contrib-requirejs-38a39c12cfe7332d.lock >> >> failed { [Error: EACCES, open >> '/Users/richardeng/.npm/_locks/grunt-contrib-requirejs-38a39c12cfe7332d.lock'] >> >> npm WARN locking errno: -13, >> >> npm WARN locking code: 'EACCES', >> >> npm WARN locking path: >> '/Users/richardeng/.npm/_locks/grunt-contrib-requirejs-38a39c12cfe7332d.lock' >> >> } >> >> npm ERR! Darwin 14.3.0 >> >> npm ERR! argv "node" "/usr/local/bin/npm" "install" >> >> npm ERR! node v0.12.3 >> >> npm ERR! npm v2.9.1 >> >> >> npm ERR! Attempt to unlock >> /Users/richardeng/amber-eric/node_modules/grunt-contrib-requirejs, which >> hasn't been locked >> >> npm ERR! >> >> npm ERR! If you need help, you may report this error at: >> >> npm ERR! <https://github.com/npm/npm/issues> >> >> npm WARN locking Error: EACCES, open >> '/Users/richardeng/.npm/_locks/requirejs-3b48fc1082eb4ee6.lock' >> >> npm WARN locking at Error (native) >> >> npm WARN locking >> /Users/richardeng/.npm/_locks/requirejs-3b48fc1082eb4ee6.lock failed { >> [Error: EACCES, open >> '/Users/richardeng/.npm/_locks/requirejs-3b48fc1082eb4ee6.lock'] >> >> npm WARN locking errno: -13, >> >> npm WARN locking code: 'EACCES', >> >> npm WARN locking path: >> '/Users/richardeng/.npm/_locks/requirejs-3b48fc1082eb4ee6.lock' } >> >> npm ERR! Darwin 14.3.0 >> >> npm ERR! argv "node" "/usr/local/bin/npm" "install" >> >> npm ERR! node v0.12.3 >> >> npm ERR! npm v2.9.1 >> >> >> npm ERR! Attempt to unlock >> /Users/richardeng/amber-eric/node_modules/requirejs, which hasn't been >> locked >> >> npm ERR! >> >> npm ERR! If you need help, you may report this error at: >> >> npm ERR! <https://github.com/npm/npm/issues> >> >> npm WARN locking Error: EACCES, open >> '/Users/richardeng/.npm/_locks/amber-dev-61951ce66a64c1a7.lock' >> >> npm WARN locking at Error (native) >> >> npm WARN locking >> /Users/richardeng/.npm/_locks/amber-dev-61951ce66a64c1a7.lock failed { >> [Error: EACCES, open >> '/Users/richardeng/.npm/_locks/amber-dev-61951ce66a64c1a7.lock'] >> >> npm WARN locking errno: -13, >> >> npm WARN locking code: 'EACCES', >> >> npm WARN locking path: >> '/Users/richardeng/.npm/_locks/amber-dev-61951ce66a64c1a7.lock' } >> >> npm ERR! Darwin 14.3.0 >> >> npm ERR! argv "node" "/usr/local/bin/npm" "install" >> >> npm ERR! node v0.12.3 >> >> npm ERR! npm v2.9.1 >> >> >> npm ERR! Attempt to unlock >> /Users/richardeng/amber-eric/node_modules/amber-dev, which hasn't been >> locked >> >> npm ERR! >> >> npm ERR! If you need help, you may report this error at: >> >> npm ERR! <https://github.com/npm/npm/issues> >> >> npm WARN locking Error: EACCES, open >> '/Users/richardeng/.npm/_locks/grunt-execute-50f558720bdf0fb6.lock' >> >> npm WARN locking at Error (native) >> >> npm WARN locking >> /Users/richardeng/.npm/_locks/grunt-execute-50f558720bdf0fb6.lock failed { >> >> [Error: EACCES, open >> '/Users/richardeng/.npm/_locks/grunt-execute-50f558720bdf0fb6.lock'] >> >> ... > > -- > You received this message because you are subscribed to the Google Groups > "amber-lang" 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 "amber-lang" 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. |
|
|
H. Hirzel wrote: > An example of a simple contribution to Amber for example could be the > addition of a method > > #perform:with: > > Amber only has > > #perform:withArguments > > But Pharo has as well #perform:with: Well, if someone new has free time to contribute to Amber, maybe he can look at existing issues and pick ones with label "entry level". And, if you feel something is lacking, an issue could be added to the tracker (there are few of them about adding new Pharo-inspired API already). -- You received this message because you are subscribed to the Google Groups "amber-lang" 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. |
| Free forum by Nabble | Edit this page |