4 ms·

A little surprised that the linked systemd file-hierarchy(7) manpage makes no mention of /opt

by i80and 1y ago

creatonez 1y ago
/opt/ is just a dumping ground for crap nobody can find a better location for
- curt15 1y ago
  Where else would ./install-3rdparty-software.sh write to? Should it spray files all over /usr?
  - creatonez 1y ago
    It shouldn't do anything until the user has told it where the files should end up. It's an unpackaged program, there is no sane place to put it that doesn't have a high chance of conflicting with something else.
    - kelnos 1y ago
      That's only due to a lack of standardization. I think a default install to a vendor-specific directory under /opt is a sane place to put it, and there's a very low chance that would conflict with something else. But sure, absolutely, an installer should prompt the user for an install location, and I think a default under /opt is probably among the best defaults possible, if we consider installing outside $HOME to be reasonable.
  - MisterTea 1y ago
    Honestly there should be no install-bs.sh and you just bind everything into the file tree as needed. At least that is how it works on Plan 9 which simplifies a lot of things like path which is just '/bin.'
JdeBP 1y ago
You won't find it in the hier(7) manual pages on BSDs, either. * https://man.openbsd.org/hier https://man.openbsd.org/hier * https://man.netbsd.org/hier.7 https://man.netbsd.org/hier.7 * https://man.freebsd.org/cgi/man.cgi?query=hier&sektion=7 https://man.freebsd.org/cgi/man.cgi?query=hier&sektion=7 * https://man.dragonflybsd.org/?command=hier&section=7 https://man.dragonflybsd.org/?command=hier&section=7 There was a long time when the Linux world held /opt in disfavour, because officially it required either a stock market ticker name or some other corporate identity to make a subdirectory legitimate. You can still see traces of this in the Solaris descendant operating systems, where pkginfo(5) talks about package names using corporate stock ticker names. * https://illumos.org/man/5/pkginfo https://illumos.org/man/5/pkginfo /opt/SUNW* used to be a very familiar thing to a lot of people. Maybe enough time has passed for anti-corporate memory to fade. Maybe there's enough corporate backing in the Linux world now to resurrect the idea regardless. Maybe /opt/RHT* is the shape of things to come. (-: I've never over the years seen the systemd people advocate for /opt, though.
WhyNotHugo 1y ago
/opt is used for manually-installed software. Packages should never place files there, so it falls out-of-scope for file-hierarchy(7) or hier(7).

A little surprised that the linked systemd file-hierarchy(7) manpage makes no mention of /opt

by i80and 1y ago

A little surprised that the linked systemd file-hierarchy(7) manpage makes no mention of /opt

creatonez 1y ago

/opt/ is just a dumping ground for crap nobody can find a better location for

curt15 1y ago
Where else would ./install-3rdparty-software.sh write to? Should it spray files all over /usr?
- creatonez 1y ago
  It shouldn't do anything until the user has told it where the files should end up. It's an unpackaged program, there is no sane place to put it that doesn't have a high chance of conflicting with something else.
  - kelnos 1y ago
    That's only due to a lack of standardization. I think a default install to a vendor-specific directory under /opt is a sane place to put it, and there's a very low chance that would conflict with something else. But sure, absolutely, an installer should prompt the user for an install location, and I think a default under /opt is probably among the best defaults possible, if we consider installing outside $HOME to be reasonable.
- MisterTea 1y ago
  Honestly there should be no install-bs.sh and you just bind everything into the file tree as needed. At least that is how it works on Plan 9 which simplifies a lot of things like path which is just '/bin.'

JdeBP 1y ago

You won't find it in the hier(7) manual pages on BSDs, either. * https://man.openbsd.org/hier https://man.openbsd.org/hier * https://man.netbsd.org/hier.7 https://man.netbsd.org/hier.7 * https://man.freebsd.org/cgi/man.cgi?query=hier&sektion=7 https://man.freebsd.org/cgi/man.cgi?query=hier&sektion=7 * https://man.dragonflybsd.org/?command=hier&section=7 https://man.dragonflybsd.org/?command=hier&section=7 There was a long time when the Linux world held /opt in disfavour, because officially it required either a stock market ticker name or some other corporate identity to make a subdirectory legitimate. You can still see traces of this in the Solaris descendant operating systems, where pkginfo(5) talks about package names using corporate stock ticker names. * https://illumos.org/man/5/pkginfo https://illumos.org/man/5/pkginfo /opt/SUNW* used to be a very familiar thing to a lot of people. Maybe enough time has passed for anti-corporate memory to fade. Maybe there's enough corporate backing in the Linux world now to resurrect the idea regardless. Maybe /opt/RHT* is the shape of things to come. (-: I've never over the years seen the systemd people advocate for /opt, though.

WhyNotHugo 1y ago

/opt is used for manually-installed software. Packages should never place files there, so it falls out-of-scope for file-hierarchy(7) or hier(7).