> I recently moved my Plex library from a Slack 14.2 box to a Slack64 14.2 > system. It is actually exactly the same hardware, from a different hard > drive. I therefore installed the plexmediaserver package from > slackbuilds.org <http://slackbuilds.org> in my Slack64 14.2. This > installs version 1.4.2, while the most recent version seems to be 1.12.3. > > The problem is that version 1.4.2 does not work in my Slack64 14.2 - in > a nutshell, videos cannot be played, because the relevant codecs can't > be downloaded by that version of the Plex server. After removing the > 1.4.2 version, I proceeded to download and install the 1.12.3 version, > by modifying the plexmediaserver.Slackbuild file from slackbuilds.org > <http://slackbuilds.org>. With this version, the codecs are > automatically downloaded, as they should, and my videos play without a > problem. > > I think that this has already been discussed in this forum, but it may > be worth the while bringing it up again: what's the point of keeping a > package that leads to a non-working installed software? I understand > that, for the sake of a stable system, as Slackware is deservedly > reputed to be, having the latest and greatest is probably not always a > good idea - although sometimes it may be. This aside, the other side of > the coin is that slackbuilds.org <http://slackbuilds.org> packages > should result in installed software that works. > > Should this not be part of the responsibility of package maintainers? I > acknowledge that this can be a pain in the neck, but it you can't do so > for whatever reason, do not maintain the package.
Have you tried to contact the maintainer? -- Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
