And this time I *will* get upset if people decide to just put blockers. As far as I can see, squirrelsh just install a binary and the shared object… no include files to link against that object, so it's an internal library. And as such, that library is *pointless* (it'll share less memory than just leaving it inside a single executable file). See also my blog post on the matter: http://blog.flameeyes.eu/2010/03/23/shared-libraries-worth-their-while So Kenneth, please see if you can make squirrelsh just link statically and be done with that, afaics that should be easy as the package has a static flag already… Also, metadata.xml is out-of-date, Evan's mail is not available on bugzilla, please fix.
Based on squirrelsh's DESCRIPTION, I suspect that squirrelsh maybe should be linking against the libsquirrel.so installed by dev-lang/squirrel. I'll have to look closer after I fix dev-lang/squirrel.
Hmm, maybe. I'll just have it use static in the meantime.
squirrelsh added some functionality to its bundled squirrel ( http://ohnopub.net/hg/SQUIRREL2/rev/4caf0440719d ) , we'll have to see if squirrelsh and squirrel are willing to work together... http://squirrel-lang.org/forums/thread/3691.aspx https://sourceforge.net/tracker/?func=detail&aid=2985125&group_id=157570&atid=804360 Is this enough to block bug 251464 ? Should I just incorporate the patch into dev-lang/squirrel without waiting on upstream?
@binki: Any news about squirrel upstream incorporating that patch?
(In reply to comment #4) > @binki: Any news about squirrel upstream incorporating that patch? Sorta/Sorta no. I have found out that there is a kind human being who maintains squirrel ;-), but there's no publically accessible VCS and no public comment on the forum thread with the patch. And so far as I've noticed there's been no change for the libsquirrel-3 betas either. What I got from the author in a private email: Date: Wed, 25 Aug 2010 21:25:44 +0800 From: Alberto Demichelis <alberto@demichelis.net> `` About autotools: the main reason I haven't said much about it is that I'm not exactly a unix expert. My last professional experience with unix was about 15 years ago and the last time I really done something with linux was before it had a binary distribution. So, I can't judge if what you guys are proposing is the best way, how much trouble it involves etc... I wonder if it's really worth for few Kb of library, to even go through the hassle of sharing it between different apps. I'd expect people to heavily customize squirrel as is an embedded language. I'd see the point if we would have a python style distro that has a bunch of libs etc... Correct me if I'm wrong. That's all I can think of :) ''
Oh, and the original forum thread link is broken because of webapp upgrades/replacements http://squirrel-lang.org/forums went through. The new ``perma''link is: http://squirrel-lang.org/forums/default.aspx?g=posts&t=1859
@Evan's I'm proxying this for you. Do you want me to help with this bug?
Upstream now provide a knob to use /usr/lib/libsquirrel3.so instead. I've enabled it for gentoo: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=80411830354cfd8f94ddd10ba83921299672a8ab
