From Issue #79November 2000
Is this still active for discussion?
Consider the mass of RPMs installed on most systems; to avoid an excessively long PATH, I would recommend mandating that /opt/bin/ be on a user's path, and that /opt//bin/ be softlinked out - this also makes those exported binaries of the package similar to the exported interfaces to an object in OOD concepts.
in /opt//bin/, what is the format of ? In past, Vendor/product/version seemed apppropriate; for example /opt/Netscape/navigator/4.79/bin/communicator This assures unique package identifiers while only assuring that vendors map their own namespace. Perhaps /opt/com.netscape/navigator/4.79. Contrariwise, I've seen the format /opt/com.netscape-navigator-4.79/bin/
I think under the definitions layed out here, "/opt/com.netscape-navigator-4.79/bin/" is the format that should be used. Personally I like only having to down the directory tree once, rather than having to go down the same branch three times to get to the bin folder.