scripts without she-bang in /usr/lib/packagename/

2011-11-17 Thread Paul Wouters
I have a package that contains ruby scripts in /usr/lib/packagename/ These scripts are only called/included via other binaries. If I do not make these executable, then rpmlint complains about non-executable content in /usr/lib/packagename/ and suggests I move it to /usr/share/packagename. If I

Re: scripts without she-bang in /usr/lib/packagename/

2011-11-17 Thread Toshio Kuratomi
On Thu, Nov 17, 2011 at 12:26:13PM -0500, Paul Wouters wrote: I have a package that contains ruby scripts in /usr/lib/packagename/ These scripts are only called/included via other binaries. If I do not make these executable, then rpmlint complains about non-executable content in

Re: scripts without she-bang in /usr/lib/packagename/

2011-11-17 Thread Paul Wouters
On Thu, 17 Nov 2011, Toshio Kuratomi wrote: When you talk about scripts, do you mean that the code calling these scripts does the equivalent of this (note, I generated my examples by reading up on ruby on the web just prior to posting... please allow for this perhaps not being real ruby code

Re: scripts without she-bang in /usr/lib/packagename/

2011-11-17 Thread Toshio Kuratomi
On Thu, Nov 17, 2011 at 01:09:47PM -0500, Paul Wouters wrote: On Thu, 17 Nov 2011, Toshio Kuratomi wrote: When you talk about scripts, do you mean that the code calling these scripts does the equivalent of this (note, I generated my examples by reading up on ruby on the web just prior to

Re: scripts without she-bang in /usr/lib/packagename/

2011-11-17 Thread Paul Wouters
On Thu, 17 Nov 2011, Toshio Kuratomi wrote: nod And also note -- the use of /usr/lib (*not* %{_libdir}) vs /usr/share is debatable (I said could above rather than should). The modules that go into the default search path, for python, perl, and ruby, for instance, all end up in /usr/lib if