Package Details: squirrel 3.1-1

Git Clone URL: https://aur.archlinux.org/squirrel.git (read-only, click to copy)
Package Base: squirrel
Description: A light-weight scripting language that fits in the size, memory bandwidth, and real-time requirements of applications like video games
Upstream URL: http://www.squirrel-lang.org/
Licenses: MIT
Submitter: None
Maintainer: Dragonlord
Last Packager: Dragonlord
Votes: 10
Popularity: 0.107752
First Submitted: 2010-12-13 11:20
Last Updated: 2016-04-12 19:53

Latest Comments

1 2 3 Next › Last »

zackthehuman commented on 2014-11-02 06:46

Squirrel 3.0.6 has been released. 3.0.6 contains a security fix for 3.0.5.

Anonymous comment on 2012-12-14 23:15

PKGBUILD updated.

Changes:
* New version of Squirrel.
* New license updated.

0x1997 commented on 2012-12-09 09:53

Squirrel 3.0.4 has been released.

Anonymous comment on 2012-11-04 22:37

License is MIT in current version.
Refer to http://www.squirrel-lang.org/

Anonymous comment on 2012-09-04 01:44

Updated. Md5 dismatch fixed. Maybe a minor update of Squirrel.

Anonymous comment on 2012-06-20 10:36

Updated with last version of Squirrel.

Anonymous comment on 2012-05-02 10:31

The author has responded me. It seems he is working on a review of Squirrel 3.0.2 for fix problems with current versions of g++. It sounds like good news :-)

Anonymous comment on 2012-04-28 20:50

Thanks, Ilgrim and losinggeneration. Judging by the activity from the project's GC page, I would not bet on upstream fixing it any time soon. I opened a ticket for the shared libs thing half a year ago, and to my knowledge, it has not been fixed meanwhile in the upstream. Upstream should find additional devs or something, open up the project a bit.

Anonymous comment on 2012-04-28 16:01

Package updated

Changes:
* Created a patch that modifies Makefiles adding -fPIC and -fpermissive. Now seems it compiles fine.

Squirrel Author has been notified about this problems with Gcc 4.7.x. I'm still waiting his response.

Anonymous comment on 2012-04-28 14:35

This issue was reported to upstream and I'm waiting some response. Meanwhile, i'll update the package with a patch to fix this.