The disadvantage to using dpkg like this is that error messages are likely to be cryptic dpkg doesn't automatically resolve dependencies or create the directory structure it expects. It used to be possible to install b with dpkg into one's home directory. The disadvantage to this approach is that you need the development environment available for this approach to work at all, and you might find yourself compiling dozens of packages in order to resolve all the dependencies. Usually this looks something like: apt-get source package apt-get source Approachįinally, you could use the apt-get source command to fetch the source of the package and configure it to install locally. When installing skype with the apt install -f command, it attempted to remove 96 () packages. That is far better than sudo dpkg -i b & sudo apt install -f in my opinion.
This is a somewhat involved process, but one you should be able find community help for as many developers set up chroot environments for compiling code. deb file, gdebi will scan for and install all of the.
schroot ApproachĪnother approach is to use schroot to create a non-root chroot. As long as all dependencies of the binary are installed, it should run as normal. Then you can export the PATH where the binary is. If the deb isn't in the Ubuntu repositories, apt-get package_name won't work, but you may be able to download it from a web site. deb Approach apt-get download package_name # replace `package_name` with the name of the package. Here you can also deinstall it if necessary.Apt doesn't support it directly, but there are ways to do it.
0 kommentar(er)
