Package Details: sonarr 3.0.6.1196-1

Git Clone URL: https://aur.archlinux.org/sonarr.git (read-only, click to copy)
Package Base: sonarr
Description: TV download automation for usenet and torrents.
Upstream URL: https://sonarr.tv/
Licenses: GPL3
Submitter: justin8
Maintainer: degeberg (fryfrog)
Last Packager: fryfrog
Votes: 82
Popularity: 0.63
First Submitted: 2014-11-10 04:45
Last Updated: 2021-03-27 22:34

Required by (7)

Sources (5)

Latest Comments

« First ‹ Previous ... 6 7 8 9 10 11

degeberg commented on 2014-01-23 20:36

As I previously said, I think that categorically stating "[in] /opt as it should be" is highly debatable.

The Arch Packaging Standard says that "/opt/{pkg}" is for self-contained packages, and "/usr/lib/{pkg}" is for libraries. I think what I've placed under /usr/lib counts as libraries used for the mono program (run via the /usr/bin/nzbdrone executable script).

Multiple other packages do something similar. I mentioned chromium earlier, but to mention a few more: r, virtualbox, erlang, ghc. I'm sure I could find more if I bothered. These are packaged by Arch Linux TUs/devs, so I think they can reasonably be regarded as an authoritative interpretation of the packaging standards. Even the mono package, which nzbdrone uses, stores its *.exe files under /usr/lib/mono and has tiny shell scripts in /usr/bin looking like "exec /usr/bin/mono /usr/lib/mono/whatever" like I do.

If you want an example from AUR, I can point to the sabnzbd package (which as a "competitor" program must be a reasonably close example for comparison purposes) that is packaged in exactly the same way as this package.

If you feel this should be changed, please do provide a compelling counterargument, and I'll of course consider it. So far I've heard nothing but "I think otherwise".

pho commented on 2014-01-23 12:15

deb is no longer available
I've changed my package to /opt as it should be

justin8 commented on 2013-11-29 12:37

This should be x86_64/i686. Any packages are for things that can be compiled anywhere and run on any architecture. exe's with mono don't fit in to that category.

And as said before, it probably belongs in /opt, but that's your choice.

Bombardment commented on 2013-11-26 20:55

Flagged out-of-date. 2.0.0.855 deb is no longer available

12eason commented on 2013-11-03 19:40

Check out the way sabnzbd, sickbeard and couchpotato do it. Even the executable belongs there, in a folder that only it has access to. /opt/ was meant for packages like this. Chromium is different, it's not a web server for a start.

12eason commented on 2013-11-03 19:28

It's a web server, possibly available over a public network. Under /usr/bin, if it were hacked it can run code as root without any privilege escalation. For security reasons it needs to be executed as unprivileged user, say nzbdrone:nzbdrone, and reside in a folder that only it owns. Check out the way sabnzbd, sickbeard and couchpotato do it.

degeberg commented on 2013-11-03 11:12

I think that's debatable. I regarded it as libraries required to execute the /usr/bin/nzbdrone executable. The chromium package works the same way. I agree that it can belong in /opt as well though.

12eason commented on 2013-11-03 10:42

Thanks for this, but it belongs in /opt/.