Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Completely agree that a package should not install to /opt, especially if it puts files elsewhere too like in /usr/bin. Imho /opt should contain completely self contained software so you can nuke it from orbit by simply just deleting it from /opt. Commented Mar 26, 2011 at 16:59
  • Okay great responses thanks but it is installed to /opt by default. If not to /opt, then where should I install it to? And how to do so using dpkg? Commented Mar 27, 2011 at 8:39
  • @Duke: If you can get the source of the deb package, you can rebuild the deb to install into the system like regular packages. This will require a little bit of work if you are not already familiar with the procedure, but imo that is the correct thing to do here. Commented Mar 27, 2011 at 8:54
  • 1
    don't agree with this answer. There are plenty of situations where you want two versions of software installed, you can easily want a specific python for a specific application. A local sysadmin might want to package this python, where should it go? Locally installed (make install) software goes in /usr/local, 3rd packaged software goes in /opt/ - the definition of packages is kept broad: via dpkg, via installers, via PIP, via (insert packaging system of choice). I agree that it is good practice of self contained "provider/packages". Commented Apr 12, 2012 at 11:34