Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - ums

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: ums 6.5.3-1

Git Clone URL: https://aur-dev.archlinux.org/ums.git (read-only)
Package Base: ums
Description: Universal Media Server: a DLNA-compliant UPnP Media Server. Build based on Java 8.
Upstream URL: http://www.universalmediaserver.com/
Licenses: GPL2
Submitter: Red_Squirrel
Maintainer: Mitch
Last Packager: Mitch
Votes: 64
Popularity: 2.192286
First Submitted: 2012-06-14 14:28
Last Updated: 2017-01-07 10:45

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Red_Squirrel commented on 2014-08-07 21:05

Another possibility is to insert all three release as sources and let the user choose later what version to install, but this requires that you'll have to download 3 different packages (each one of about 30MB) and I don't think it is a very good idea xD
About Java7 yes, it's true that it is the only one in Arch official repos, but since this is an AUR package I don't think that people who want to install this package using AUR have big problems to install another package from it ("jre" I mean) xD And about the uninstallation of Java 7 to install Java 8, it's perfectly normal because Java has always the backward compatibility, so all applications that requires Java 7 will work flawlessly even with Java 8, no need to worry about it.
So, at the end, the only issue with using Java 8 is maybe that many users should upgrade their JAVA environment and it could be a pain in some situations (slow internet connections, old or fixed systems, weird configurations, etc...).
So... yeah the situation is really debatable and I really don't know what's the better choise XD
For now I think the wisest thing to do is to leave the easy-editable PKGBUILD waiting the development of the 3-builds situation in next versions :)

headkase commented on 2014-08-07 20:42

Well, I installed "jre" from AUR to get Java 8. UMS works fine with that. It is still your choice however, on my own machine I had to uninstall Java7 before 8 would install. As UMS is the only application I use Java for that was no issue. Other people however might require Java7 for other programs. I don't know what is the least complicated path to minimize those issues. Probably exactly what you've done now - have an easily editable number in the PKGBUILD.

headkase commented on 2014-08-07 20:14

I'm using Java7 because it is in the official repos:

extra/jre7-openjdk 7.u65_2.5.1-3 [installed]
OpenJDK Java 7 full runtime environment

That would seem to make it a logical default. However, it's your package so it's your choice. Perhaps waiting to see what the UMS developers themselves do would be prudent - it IS easy enough to edit the PKGBUILD..

Red_Squirrel commented on 2014-08-07 19:57

However if you say me that JAVA 7 is better as default choise I have no problem to use it. If there are not significant changes in perfomance we can use JAVA 6 too, in this way the pkg will be compatible with also more systems ;)
To say the truth when I saw the new release I thought about to create 3 different pkgs but then I realized that we really don't know if the authors will build them every release from now on, so I decided to wait for next releases to confirm or less their future intentions xD

Red_Squirrel commented on 2014-08-07 19:43

"jre" is the official Java Runtime Environment package. It's in AUR and not in official Arch repos (I think because it is not fully opensource since it belongs to Oracle). Its version currently is "8u11-1" ;)

headkase commented on 2014-08-07 19:38

Excuse my lack of being able to find it, but, where is Java 8 in either the main repos or AUR? Defaulting to 8 leaves UMS unable to launch on my system where I have 7 installed. It is trivial to change the version, as you said and I did, but would defaulting to 7 be better for this package?

Red_Squirrel commented on 2014-08-07 08:02

v4.0.2 has been released in three different builds for Java 6, 7 and 8. This package simply use the latest one (for Java 8) but if you need Java 6 or Java 7 version just edit the PKGBUILD changing the "_javaver" var to the Java version you want (the sha1sums are already present for all the builds) ;)

Red_Squirrel commented on 2014-06-26 21:06

Updated (downgraded?) to the latest v3.6.3 as requested.
To avoid to go back and forth with the versions, from now on only the full versions will be added. In other words no more alpha, beta, etc... here in future.

Red_Squirrel commented on 2014-05-27 08:40

Updated to v3.6.2 (again)

Red_Squirrel commented on 2014-05-25 18:39

Restored to v3.6.1.