[Slackbuilds-users] Plex version too old

[JCA]

Speaking for myself, that would be terrific, and much appreciated.

On Thu, May 3, 2018 at 3:49 PM, Andrew <andrew at stevens.is> wrote:

> I use and am willing to maintain plexmediaserver if no one has any
> objections. But unfortunately I won't be able to submit a diff until
> Saturday if that is alright?
>
> Regards,
>
> Andrew Stevens
> andrew at stevens.is
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On May 4, 2018 9:34 AM, JCA <1.41421 at gmail.com> wrote:
>
> I am not interested in becoming a package maintainer, in part precisely
> because I am all too aware of what is involved. I am very thankful that
> there are people willing to do so. I am merely pointing out that, if they
> can't or won't do what is concomitant to maintaining a package, they should
> not volunteer - it is obvious that, if the Slackbuilds packages are poorly
> maintained, Slackbuilds loses reliability and credibility.
>
> On Thu, May 3, 2018 at 2:51 PM, B Watson <yalhcru at gmail.com> wrote:
>
>> On 5/3/18, JCA <1.41421 at gmail.com> wrote:
>> > This aside, the other side of the coin is that
>> > slackbuilds.org packages should result in installed software that
>> works.
>> >
>> > Should this not be part of the responsibility of package maintainers?
>>
>> At the time it was submitted, I bet the package worked fine.
>>
>> You're right, the maintainer should be updating it. But, this happens all
>> the time: someone submits a SlackBuild for a piece of software they use,
>> and then a year or two later, they stop using that software for whatever
>> reason... or possibly they stop using Slackware and switch to another OS.
>>
>> If we're very lucky, the maintainer will post a message to this list
>> saying "I'm giving up my builds, here's a list of them". But all too
>> often, it happens silently.
>>
>> The answer is: now that you're using plexmediaserver, you should take
>> over as maintainer. Try to contact the old maintainer first, either to
>> get permission or to verify that they're not responding... if you don't
>> get a response within a few days, post a message to this list announcing
>> you're taking over as maintainer.
>>
>> If you're not willing to step up and be a maintainer, it's not very
>> helpful to say things like this:
>>
>> > 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.
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180503/6da63e09/attachment.html>