- #J. RIVER MEDIA CENTER 25 INSTALL#
- #J. RIVER MEDIA CENTER 25 UPDATE#
- #J. RIVER MEDIA CENTER 25 REGISTRATION#
I'm using this guys handbrake image and it's really great to use! But I didn't succeed doing that (yet) with JRiver. Also has something to do with that I wanted to maybe make my own docker image for MC25 based on this image witch would allow you to get VNC access with a browser.
#J. RIVER MEDIA CENTER 25 INSTALL#
So I can just purge it and install another RPM from the bunch I'll have by then.Īll of my music is on a JRiver instance on my NAS and I remote play it on every PC and that one still runs a version of MC24, because it worked and I didn't bother to upgrade it yet. Thankfully, I do not have a big problem with it breaking on my PCs since on all of them I don't have any music. Since I won't have anyone validating if it worked or not when I do it myself. Witch is probably the best I can do for myself anyways. The next step would be to create a 'nightly' dnf repo automatically. Except it does not tell me in any way that there might be a new version it built or install the rpm with dnf upgrade. I think this is already a bit better than running the script on every machine. But since I wasn't planning on installing it on the machine making the RPMs, there was really nothing to query. I'm not sure how dnf repos are hosted and what goes into that, but I probably can query that if I do that. But that's nothing I'm gonna do currently but a bit later maybe.Ībout saving the version number in a text field. Ideally I would like it to not only make the RPMs ready for use, but also host a DNF repo on that headless machine. It's a headless Fedora 30 Server install on my NAS without a desktop environment that makes the RPMs now and then I can install them on PCs I actually use. I'm not really installing jriver on the VM that runs that script now. It also saves the version number into a file and only tries to make a new rpm if the version number is either not there or the new one from interact is greater than the old one. Quote from: max096 on May 25, 2019, 12:00:02 pm So that's what I ended up with for the time being. I put a line similar to this into the crontab of my user. I modified the script a bit, now it works fine. Not that it really matters since it's a home folder on a VM that's gonna do essentially nothing else. Ok, it technically works, but dumps all the things into my home folder instead of the folder it should be in. (Not a replacement for BryanC's script I deleted the entire "actually install the thing" portion and some user inputs, because that's not the goal I have in mind for this.) I'm not sure this works when I put this into a cron job yet (hope it does "just work"). (btw, Upload isn't actually Uploaded anywhere if you are wondering, that's just in my local network ) It also saves the version number into a file and only tries to make a new rpm if the version number is either not there or the new one from interact is greater than the old one.Īnd then moves the RPM to a folder specified. So that's what I ended up with for the time being. Check for RPMFusion repos in -install-repo mode (13-JUNE-2019, v0.9)ģ5. Removed dist tag for simpler cross building (04-JUNE-2019, v0.8 )ģ4. Another refactor, removed explicit -a mode (redundant, just omit the version number) (04-JUNE-2019, v0.8 )ģ3. Added new mode to install the new MC repo (01-JUNE-2019, v0.6)ģ1. Readd support for old syntax without version flag (./install_MC_fedora.sh 25.0.44) (2, v0.4)ģ0. Explicit version numbers can be passed using the new flag (2, v0.3)Ģ8. Added optional flag for automatic version scraping (2, v0.3)Ģ7. Added optional flag for cross-building on unsupported OSes (2, v0.3)Ģ6. Complete refactor in preparation for repo (2, v0.3)Ģ5. Automatic mode will not attempt to build/install the same MC version, better for cron or systemd timers (2)Ģ4. Added RPM check so the RPM is not rebuilt if it already exists in the BUILD directory (2)Ģ3. Added an automatic mode if no version number is specified (2)Ģ2.
Add test repo check for beta versions (2)Ģ1. Make rpmbuild error output noisier (2)Ģ0.
#J. RIVER MEDIA CENTER 25 UPDATE#
Update security limits file naming for upcoming JRiver Media Center 25 (2)ġ9. Add security limits file to rpmbuild (0)ġ7. Add some silent logic for future CentOS support ( CentOS 8) (2)ġ6.
#J. RIVER MEDIA CENTER 25 REGISTRATION#
Install and symlink ca-certificates files for license registration (2)ġ2. Check for RPMFusion repos before installing dpkg and rpm-build (2)ġ0. DNF may erroneously report a downgrade the first time the new package number is installed. MC point versions are now stored as the variation number. Changed versioning system used in rpmbuild.
Script is now MC version agnostic and self-contained (2)Ĥ.
Added test for rpmfusion repos (and add if necessary) (2)ģ. Added test for rpm-build package (and add if necessary) (2)Ģ.
Code: mediacenter25 /RestoreFromFile "~/Downloads/Media Center25 Master-XXXXXX.mjr"ġ.
0 kommentar(er)
