I had a look and JASP technically needs no admin privileges. Admins are also lazy and dependent on your organization, you must first explain why a program is important for your work, then the IT guys must check if giving a new program admin privileges might be harmful to the system etc.īut there is no need for this hassling.
This is impossible because JASP's installer requires admin privileges, which one of course doesn't have (my colleagues at the University also don't have admin privileges). As long as all dependencies of the binary are installed, it should run as normal.I wanted to try out JASP on my PC at work. Then you can export the PATH where the binary is. 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.Īs dpkg -i doesn't work (see comments), I suggest this alternative: dpkg -x b dir Usually this looks something like: apt-get source package 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.įinally, you could use the apt-get source command to fetch the source of the package and configure it to install locally. The following example will install b into your home directory. Once you have your deb file call dpkg directly from the command line. Replace package with the name of the package
You may be able to download this from a web site or if it's in the Ubuntu repositories you can download with. The second way I know of is to install from a. 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. One is to use schroot to create a non-root chroot. Apt doesn't support it directly, but there are ways to do it.
0 kommentar(er)
