Package Details: opa-bin 1.1.1-1

Package Base: opa-bin
Description: Rapid + Secure Web Development
Upstream URL: http://opalang.org
Category: devel
Licenses: MIT AGPL
Submitter: exterm
Maintainer: cju
Last Packager: None
Votes: 6
First Submitted: 2012-08-01 17:45
Last Updated: 2013-04-22 12:14

Dependencies (3)

Required by (0)

Sources

Latest Comments

Comment by cju

2013-04-13 12:21

Hello,
I've taken the place of exterm as Maintainer of this package. Version 1.1.1 will arrive in a few days so I will skill the current 1.1.0.
Many thanks to exterm for the work done previously.

Comment by exterm

2013-01-20 16:11

I no longer use opa at the moment. Is someone willing to adopt this package?

Comment by exterm

2013-01-20 16:11

Nice, thanks @Qoru.

Anonymous comment

2013-01-19 22:34

I can confirm that filetype detection and syntax highlighting in vim works.

Comment by exterm

2012-11-11 13:10

updated to 1.0.7. Sorry for taking so long.

Thanks @pisuka for the PKGBUILD, I took some things from it.
I would be happy to incorporate more changes from that PKGBUILD if someone can explain the benefits ;-)

Also, I don't use vim, can someone verify that the vim integration works?

Comment by pisuka

2012-11-10 03:50

http://paste.ubuntu.com/1346875/

Comment by exterm

2012-10-17 14:16

opa 1.0.7 is out. Will update the package as soon as possible.

Comment by elegua

2012-09-08 01:34

As far as I can tell, this is the new normal for npm apparently for version management reasons. From what I can tell, globally installed npm packages aren't linkable unless you expressly link them using npm link <package>. When you npm install without -g, then it installs libraries to ./node_modules and I can only compile projects with a root directory in the same directory as node_modules. Globally installed packages with command-line interfaces do seem to work without adjustment. So, it seems to me, although it is a bit clunky, it is working as intended.

Anonymous comment

2012-09-02 06:56

Okay, this seems really strange: Looks like I can only run

% opa create test

in ~/ . In any other folder I get the error I reported.

Anonymous comment

2012-09-01 09:23

Hi exterm,

thanks for that tip. I tried this but it couldn't solve my problem. (I put it in my ~/.zshrc.local because I'm using zsh.) I also updated to the recent version of opa-bin but still got the same error.

niklaas@len-t420 ~ % echo $NODE_PATH
/home/niklaas/.npm:/home/niklaas/.npm:

So my changes took effect but it doesn't help anything.

The only thing that helped was not installing the node modules globally, indeed just with running "npm install <modules>" (without "-g"). Now it works. Do you have a clue why? Is this a bug?

Comment by exterm

2012-08-27 11:00

Added 32bit support via the new 32bit binary from opalang.org

Comment by exterm

2012-08-27 10:59

Hi niklaas,

the first line is only a warning and should not cause any problems.

The second line is probably printed because opa can't find the node modules. I myself did not install the modules globally so I ran just

% npm install mongodb formidable nodemailer simplesmtp imap

but that didn't suffice, I got the same error as you. It seems that is a problem with the nodejs package. I had to add ~/.npm to the NODE_PATH too.
I added this line to my ~/.bashrc and everything was fine afterwards:

export NODE_PATH=$HOME/.npm:$NODE_PATH

Please get back to me if that doesn't work.

Comment by exterm

2012-08-27 10:13

Hi niklaas,

the first line is only a warning and should not cause any problems.

The second line is probably printed because opa can't find the node modules. I myself did not install the modules globally so I ran just

% npm install mongodb formidable nodemailer simplesmtp imap

but that didn't suffice, I got the same error as you. It seems that is a problem with the nodejs package. I had to add ~/.npm to the NODE_PATH too.
I added this line to my ~/.bashrc and everything was fine afterwards:

export NODE_PATH=$HOME/.npm:$NODE_PATH

Please get back to me if that doesn't work.

Anonymous comment

2012-08-27 08:33

Hi, I get the following error

% opa create chat
This version of node (v0.8.5) has not been tested with Opa. Use it at your own risks. The last known supported version is v0.8.2
5 modules are missing. Please run: npm install -g mongodb formidable nodemailer simplesmtp imap

even after installing the needed packages with npm.

Comment by exterm

2012-08-14 09:22

at the moment, this is 64 bit only.

Comment by exterm

2012-08-02 14:41

build 2988 should work now.

Comment by exterm

2012-08-02 14:22

yes, I also get an md5 error when traing to run the 2988 install script.
I have filed an upstream bug report: https://github.com/MLstate/opalang/issues/79

Anonymous comment

2012-08-02 13:59

I tried the build 2988 but the package seems to be broken (always get ms5-missmatch after running it).

Comment by exterm

2012-08-02 13:58

rebuilding now. Should finish the package in a few minutes.

Anonymous comment

2012-08-02 13:51

Hello, this should be fixed in build 2988. The 1.0.5 build 2980 was not the final one. Could you rebuild a package ?

Anonymous comment

2012-08-02 13:31

Does anyone ever get `opa create myapp` working? It doesn't seem to find the opa node packages. It returns:

“Opa dependencies are missing, make sure your NODE_PATH is correctly set up. You can have a look at the head of this file for hints about where Opa modules might be installed.”


I can add /usr/lib/opa/static to NODE_PATH to come to the next error (Cannot find module 'unix.opp') and finally add /usr/lib/opa/stdlib to get to where I'm currently stuck: Cannot find module 'stdlib.core.opx'.

Comment by Drup

2012-08-02 13:03

Great, the installation is working now, but not the native backend (--back-end native when compiling) is not working (lacking /usr/lib/opa/stdlib/stdlib.qmlflat, upstream bug).
For the nodejs backend, you need to set NODE_PATH=/usr/lib/node_modules (opa runtime is looking in /usr/local/lib/node_module by default). You can see it by looking inside a produced .js file.

It would be a good idea to set it when installing the package, since it's needed. Or maybe talk to the nodejs package maintainer.

Comment by exterm

2012-08-02 12:54

Please provide more information about the occuring error.

this works on my computer:

$ opa test.opa
$ ./test.js

Comment by exterm

2012-08-02 10:13

Should be fixed.

Comment by Drup

2012-08-02 05:52

I got the (beautiful) following error :
/usr/bin/opa: ligne16: /tmp/yaourt-tmp-gabriel/aur-opa-bin/pkg/usr/lib/opa/bin/opa-bin: Aucun fichier ou dossier de ce type (No such file, sorry, french ;)

also, nodejs and mongodb should be at least optional dependences

Comment by exterm

2012-08-01 17:51

There may be some dependencies missing. Please report if you find them.