[Slackbuilds-users] need some advice (re: splix/jbigkit SBos)

[Ryan P.C. McQuen]

 >I solved the issue on the home front with a symlink

The spotify64 build uses symlinks to solve library compatibility issues:

http://slackbuilds.org/slackbuilds/14.1/multimedia/spotify64/spotify64.SlackBuild

You may find it helpful (although I'm not saying this is the best solution
;-).

---
<ryanpcmcquen.com>
On Nov 25, 2014 8:33 AM, "Heinz Wiesinger" <pprkut at slackbuilds.org> wrote:

> On Tuesday 25 November 2014 12:26:09 Glenn Becker wrote:
> > Hi all,
> >
> > I've been maintaining the SlackBuilds for splix and jbigkit. For a
> > while, printing has been an issue with my Samsung ML-2510, but I've
> > been too lazy to follow it up (obviously I don't print at home very
> > much). Not very responsible of me.
> >
> > Anyhoo, the root problem is that splix development appears to have
> > stopped -- or at least greatly slowed. The current version of splix
> > looks for the library libjbig.2.0.0 ... but the current version of
> > the jbigkit library is libjbig.2.1. splix looks for v. 2.0.0, can't
> > find it and plotzes.
> >
> > I solved the issue on the home front with a symlink, but was wondering
> > what SlackBuild best practice I should use in a case like this. Should
> > I roll back the jbigkit version?
>
> Did you check how other distros solve the problem? With quick checks I see
> that both Arch and Fedora seems to have splix using jbigkit 2.1 in their
> repos.
>
> Grs,
> Heinz
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20141125/adabd66a/attachment.html>