Where to Install My Products on Linux?

 in
The details on proper application location.
______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Where to Install My Products on Linux?

amaruk's picture

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/

Re: Where to Install My Products on Linux?

Anonymous's picture

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.

Webcast
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions