[Slackbuilds-users] bug in id3-0.78 (slackware 13.0)
skalkoto at gmail.com
Fri Mar 26 15:01:08 UTC 2010
Thanks for the reply, and sorry about that! I should have paid more
attention to the FAQ.
P.S:I was talking about the id3 packages specifically, when I
mentioned the "necessity" of the existence of a binary executable. :-)
On Fri, Mar 26, 2010 at 4:39 PM, Heinz Wiesinger <pprkut at slackbuilds.org> wrote:
> On Friday 26 March 2010 15:34:14 Nikos Skalkotos wrote:
>> Hi there,
>> I think I found a bug in the script of the package. I'm using
>> slackware-current but I don't see how this matters in this case.
>> When I try to run id3.SlackBuild it stops in line 61 (the second "find"):
>> ( cd $PKG
>> find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | \
>> xargs strip --strip-unneeded 2> /dev/null || true
>> find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | \
>> xargs strip --strip-unneeded 2> /dev/null
>> The problem Is that the package does not create any libraries, so in
>> the above line the strip command fails and creates an error.
>> I think you should either completely remove the line from the script
>> or at least add a "|| true" in the end to let the script continue
>> after this.
>> Also, I don't really see any reason to have "|| true" in the previous
>> line. An executable should always be present in the package.
> Known issue, see http://slackbuilds.org/faq/#bash4
> And, fwiw, I see no reason why a package should always have an executable.
> What's with python packages, or library-only packages?
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
More information about the SlackBuilds-users