Arch Linux User Repository

joshka: The rationale behind the move to /var is that, as its name implies, it is a variable directory where programs can write all sorts of stuff, and most of it isn't tracked by pacman. /var/lib is where we put $HOME for system users, or any other users created just for the purpose of running a particular piece of software. In most cases programs should not be allowed to modify anything under /usr or /opt, plus it is easier to move your configuration if it is in a dedicated directory. Now doing the move in the install file is against arch' policy (install should not, in most cases, manipulate your files), so at best I can add a message displayed upon upgrade, and I will. As for the naming, I chose to add hyphens to pkgname for a purely cosmetic reason, I prefer to keep upstream's naming for the actual files. Also, /var/lib/plex should remain as it is, because it's the plex user's home. You could use the same plex user and its home to build an HTPC running Plex Home Theater standalone for example (better than giving it root rights). I didn't change the temp directory, it is still set to /tmp in the conf file (or did I miss something?). As for tmpfs, first thing I usually do is "systemctl mask tmp.mount", because you can easily run out of space when you have limited ram. I'm not sure how Plex does its transcoding since I've never used it before, but if it does keep the whole file in /tmp, as you said you might run into issues with larger movies, disabling tmpfs would be a good idea. Regarding why I picked rpms over debs, there are several reasons: - libarchive, hence bsdtar, has had support for extracting rpms for more than a year now, you no longer need rpmextract. - Fedora is a lot closer to Arch than Ubuntu is, being systemd-based, you can usually just copy over their unit files and configuration (not in this case though). -Finally, rpms don't have sub-archives, you don't need an extra step to unpack data.tar.gz. Thanks for mentioning the thread, I wasn't sure what the best place to contact them about this was.

Hi again, Another quick question, what's the difference between the deb package and the rpm? Or was this just about consistency with pht?

Hi Alucryd, I like that you've gone to github for this. Should make fixing things quicker. I wonder if it might be a good idea to do the app support folder move automatically during the upgrade, alternatively detect an existing install and use the installed folder so as not to break. What are your thoughts on this? I'm sure there's a good reason for the move (i.e. /var is the 'right' place for this sort of thing). Can you expand on the reasoning a bit? This might help work out whether it's better to move or leave be. Would it make sense to prompt for what to do here? Regarding legal aspects. I got in touch with legal@plex about another issue a few days ago. (plugins don't have any explicit licensing). I just mentioned your thread in an email to the plex legal council. Lastly, do you have any particular thoughts on whether all of the parts of the package should be named plex-media-server vs plexmediaserver (folders etc). Shouldn't the application support folder be /var/lib/plex-media-server? I wonder also if you could explain the change from /tmp to /var/tmp. I haven't played much with transcoding, but I wonder whether this would hit the half RAM size max limit on tmpfs for larger movies. (https://wiki.archlinux.org/index.php/Tmpfs)

For those migrating installations, the Application Support directory is now /var/lib/plex and is owned by plex:plex, pms will write everything it needs in there. Please stop pms and move your existing Application Support directory in there before updating.

Thanks for the quick answers guys. I'll upload plex-media-server and merge this one into it. hjmuller: Regarding Plex for ARM, Arch Linux ARM is already providing an armv5 build their repos afaik. There's also RasPlex if you wish http://www.rasplex.com/index.html.

Correct me if I'm wrong, but I believe we get the binaries from Plex to build this pkg, and they are all x86.. And plex media server is proprietary, so unless Plex builds it for ARM (or releases source code) you probably won't see it. But honestly, since you are seeing plex being installed on TV's and such, seems like a request over in their forums to support Plex on Raspberry Pi wouldn't fall on deaf ears. It's a win/win for everyone.

Does this mean we'll have any ARM builds for plex? I'v been wanting to run plex on my arch/raspberry pi set up without doing a full Rasplex install.

Sounds good to me.

+1 for my vote. Always better to have it in [community] and supported by you fine fellows :)