Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8320 - pkgs installing into /opt should inform users about the PATH issue

Attached to Project: Arch Linux
Opened by Jens Adam (byte) - Tuesday, 16 October 2007, 07:49 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 06 May 2008, 20:09 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I don't want to start a debate about the pros and cons of using /opt, just make it mandatory for all packagers putting stuff there (and in /etc/profile.d/, hopefully) to inform users about it in the .install.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Tuesday, 06 May 2008, 20:09 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comments
Comment by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 19:08 GMT
Aaron, should this FR be "implemented" by submitting a message to arch-dev-public? :P
Comment by Aaron Griffin (phrakture) - Monday, 10 March 2008, 18:45 GMT
Hmmm. Sorry this one went by the wayside a bit.

I am curious as to what packages you're talking about? Currently, we are trying to get rid of /opt as much as we can, so where does this apply?
Comment by Jens Adam (byte) - Wednesday, 12 March 2008, 02:01 GMT
I'm talking about everything that
1) installs into non-standard paths
2) supplies some shell snippet for /etc/profile.d
3) doesn't mention anything about this in an .install file

Packages like Google-Earth or Quake2 that have wrappers in /usr/bin don't count, but this still applies to KDE and (Sun) JRE.
I think Firefox was the top issue when I originally posted this, but as you said... wayside.
Comment by Aaron Griffin (phrakture) - Wednesday, 12 March 2008, 16:43 GMT
So, how do you expect us to make it mandatory, especially when the packages you've mentioned are community/AUR packages.

I'd suggest adding something to the wiki packaging standards, but I don't know how much I personally will be able to enforce this. Considering we're trying to kill opt off for official packages, it's really only a big deal for community packages, correct?
Comment by Greg (dolby) - Monday, 05 May 2008, 21:43 GMT
This is the first report jra has made i disagree with. I second phrakture's latest comment. Its a jon the TU of the package if they want to include .install messages warning the users about it.
Comment by Jens Adam (byte) - Monday, 05 May 2008, 22:38 GMT
Heh, may I take that as a compliment? Yep, close it, it's not an issue for me any longer.

Loading...