NextPVR on a Pi

[mvallevand]

I provided you the information you asked and then additional information in case you wanted a followup about the installation letting you know you are largely on your own to save you some time so that is hardly irrelevant.

Martin

[krazeedrivr]

I provided you the information you asked and then additional information in case you wanted a followup about the installation letting you know you are largely on your own to save you some time so that is hardly irrelevant.

Martin

Martin, thanks for all your responses....


So if anyone ELSE reading this is the author of the NextPVR/nextpvr_arm32v7 docker image and is willing to support it, please let me know if you can look at the perl implementation in your image.  Thanks!

[mvallevand]

I didn't realize that you really just wanted sub to add some more things to his image, I thought your main concern was if the image was valid. That is part of the trouble with hijacking threads and not creating a relevant topic.

My suggestion would be to open a bash shell into your Docker, add what is required to make perl work via apt and let sub know what you think he should add. He did do this for Intel graphics.

However the reason there are community builds is that sub doesn't try and make it a complete OS for all users needs leading to the advanced transcoding file processing builds, and python3 builds etc. Normally these are on amd64 because large Dockers make sense there. On small memory constrained SoC systems running native makes customization and "tinkering" much easier.

Martin

[krazeedrivr]

I didn't realize that you really just wanted sub to add some more things to his image, I thought your main concern was if the image was valid. That is part of the trouble with hijacking threads and not creating a relevant topic.

My suggestion would be to open a bash shell into your Docker, add what is required to make perl work via apt and let sub know what you think he should add. He did do this for Intel graphics.

However the reason there are community builds is that sub doesn't try and make it a complete OS for all users needs leading to the advanced transcoding file processing builds, and python3 builds etc. Normally these are on amd64 because large Dockers make sense there. On small memory constrained SoC systems running native makes customization and "tinkering" much easier.

Martin

I don't know who "sub" is, and I don't know why this "sub" is not responding instead of you... Are you an employee of NextPVR running blocker for him? I don't know why we keep having a conversation you and I, but I don't now nor ever did want to talk to you. I want to talk to the author.

I'm not asking for an "add" for the image. The perl implementation that is there is broken and needs fixed. I already tried fixing it via apt and CPAN, but there is a dependency hell with PERL and linux in the image. Even reinstalling PERL within the image is not fixing that. It needs to be resolved in the image itself before build.

[mvallevand]

In my first reply that you dssed I explained sub was the author of NextPVR.  The official announcement is here https://forums.nextpvr.com/showthread.ph...#pid522450 is from sub.

You would need to explain what is needed for sub to consider this, hopefully you can figure that out 

Martin

[mvallevand]

Thanks for taking the time to document this in your other post. It also gives sub some ideas if he wants to update his image. I will post some comments here to keep the other post clearer for potential users.

From my experience customizing a Docker changes inside Docker will get overwritten on NextPVR updates. It is best to also script the installation step and save it outside Docker. Review any command line options to ensure things are written outside Docker too

Sub's Docker is dedicated function with limited risk exposure so there are other security considerations when you introduced general scripting that you may wish to document. Many users run Docker as root and this is really bad practice for perl and python scripts, make etc, so changing the Docker user would be advised. The Docker base OS is not updated frequently, I would also advise apt update and apt install being run when you install the script and follow advisors.

Finally note that attachments have to be zipped should you want to provide any scripts.

Martin

[BrettB]

I don't know who "sub" is, and I don't know why this "sub" is not responding instead of you... Are you an employee of NextPVR running blocker for him? I don't know why we keep having a conversation you and I, but I don't now nor ever did want to talk to you. I want to talk to the author.

As Martin has already told you, and as is shown all over this forum, sub is the sole author of NextPVR. (In his spare time! There are NO "employees" of NextPVR. There is a good, helpful, and responsive support community, though.)

Additionally, sub happens to be on holiday this week, so is it perfectly justified for him not to be actively monitoring the forums and responding to non-critical questions. Martin was trying to be helpful and give you answers to your questions and point you in the right directions. He has also developed many of the additional tools used with NextPVR and is most definitely the 2nd most knowledgeable about all things NextPVR (after sub, of course).

Based upon your responses above, it seems that NextPVR (with a single volunteer author, no purchase cost, community support, and design philosophy of simple basic configuration with much more extensible configuration options possible) is probably not the right solution for your needs.

[krazeedrivr]

Just the responses I'd expect from a bunch of bitches. Fuck you, this forum, and this product. I've deleted my howto on fixing this image and getting Zap working. Thanks for nothing assholes!

[sub]

The question I had is if the docker image I found on docker hub was created by anyone @ NextPVR, and if so if they (the author) is on this forum and is willing to support it. 

That's me.

I don't know who "sub" is, and I don't know why this "sub" is not responding instead of you...

I wasn't responding because I'd been away on vacation for the last week and a half.

2. If it is an official image, is it supported, and even updated?

Yes, it's supported and gets updated every release.

I'm not asking for an "add" for the image. The perl implementation that is there is broken and needs fixed.

I hadn't intentionally added perl to this container. It's based on the mcr.microsoft.com/dotnet/aspnet:6.0 image, with NextPVR and a couple of other requirements added. As the guys said, if you can do some leg work to work out what packages needed to be added/updated to get perl working, I'm happy to roll these updates into the next release.

Just the responses I'd expect from a bunch of bitches. Fuck you, this forum, and this product. I've deleted my howto on fixing this image and getting Zap working. Thanks for nothing assholes!

Ok, nevermind then.

[mvallevand]

I actually made a copy of his other post before he deleted it since I was going to put the notes on the wiki for those that want zap2xml on Linux. I can pass the file to your if you'd like

Perl like python3 isn't in the container so there probably is a need for improvement but at the same time if your are going to allow scripting you probably need to keep Debian patchs up to date too.

Martin