I know that this is a convention we've followed (and is represented on the ebuild howto guide), but is it set in stone?
The reason I ask is that I have a group of about 5 packages that I'm working on ebuilds for that by default all want to be in /opt/Pkgname-version. I've done some ebuild foo to make it want to install stuff in /usr/bin, /usr/lib, etc, but it also contains some extra specification files that get used at runtime that it's expecting to easily find, and leaving everything to just go into /opt/Blah is so much easier to support. So my question is: is it accept to install a package into /opt that isn't strictly binary, but by default and design convention wants (and pretty much needs) to be installed there? I guess moreso I want to propose changing the 'gentoo convention' for /opt to add in that it's okay to install something in /opt that was designed to go there by its upstream authors. Thanks, Caleb -- gentoo-dev@gentoo.org mailing list
