3 ms·
> I always just used `--prefix="$HOME"` so that everything went into `~/bin`, `~/lib`, `~/man`, etc... Forgive my ignorance, but how do you uninstall stuff a y
by BeetleB 3y ago
> I always just used `--prefix="$HOME"` so that everything went into `~/bin`, `~/lib`, `~/man`, etc...
Forgive my ignorance, but how do you uninstall stuff a year or two later?
- oarsinsync 3y ago`rm`, everything’s contained within your homedir.
- fransje26 3y agoDon't forget the `-fr *` parameters.
- BeetleB 3y agoWith the described setup: > I always just used `--prefix="$HOME"` so that everything went into `~/bin`, `~/lib`, `~/man`, etc... You can't just use rm as a blunt instrument. ~/bin will contain lots of binaries from lots of packages. You want to uninstall only one package. How do you know which files correspond to that package?
- Karellen 3y ago`make uninstall` (If a project's build system does not provide an "uninstall" target (coughcmakecough) then the project likely has other deficiencies and should be avoided.)
- BeetleB 3y agoWouldn't that require me to keep the source code for that particular version lying around?
- Karellen 3y agoWell, yes. I mean, you could probably get away with just keeping the `Makefile` around. But for the stuff I installed from source, I was often interested in keeping the source code around anyway, for curiosity's sake. And hard drives are big, while source code trees generally aren't - comparatively speaking.
- BeetleB 3y agoFair enough. In that job I was working on a remote Linux system that was quite outdated. So everything I wanted to install (newer version of Emacs, etc) required me to build so many libraries, as the system ones were too old (Emacs alone required 50-100). I didn't want the hassle of keeping all the source code around.