You are not logged in.
Greetings.
I am relatively new to the world of Linux, and while google has helped me thus far, I can't seem to solve this one: How do I effectively keep record of all the files being installed, when building from source?
When everything is done through Pacman or the AUR, it's all in a system; however, not when building it manually..
Some sourcefiles has an "make uninstall"-function, but not all.
I kinda feel that I don't have control over what's happening on my system, how do I solve this?
Thanks.
Offline
The best practice is always to create PKGBUILDs for all source-based installs - this ensures that pacman will keep track of your packages i.e that you can uninstall easily and at will.
My best advice is to learn to write PKGBUILDs.
Offline
Thanks for replying. I've thought about it, but hoped there was an easier way. Guess I'll have to just dive into it, then
I was hoping the sourcefiles had a filelist, but so far I haven't located it.
Offline
I only recently learned how to create my own packages. It was so easy! You can read about it here: http://wiki.archlinux.org/index.php/Building_Packages That link also provides a simple example "PKGBUILD" file.
As you can see, the "build" function in the PKGBUILD file is nothing more than what you would do to build the package by yourself. But, by creating a PKGBUILD file, using the "makepkg" command, and then installing it with "pacman -U package.pkg.tar.gz", you can easily uninstall it in the future.
If you want, you can then upload your PKGBUILD file to the AUR, and feel good as an Arch Linux contributor.
I found it interesting that Arch Linux doesn't even setup "/usr/local/bin" in the PATH by default. It's probably for the best. It keeps me from being naughty.
Offline
If you don't want to make a PKGBUILD some software is nice enough to come with an uninstall script or an uninstall make target (ie: make uninstall). Making a PKGBUILD isn't hard and can come in handy so I'd still recommend that though.
Offline
+1 for learning to create your own packages. This will keep your system clean and provide a sane way to manage what you have on it. As mentioned above, submitting your packages to the AUR is also a great way to contribute to the community.
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
Not a coding question, moving to Newbie Corner.
Offline
Package creation is a really simple process. Just go to AUR and find a package that's close to your own: JAVA, C, Python, etc. all have little idiosyncrasies that others have solved before. And there's always IRC, if you need "real time" {help|mocking}.
Offline
Thanks guys -- I've played around with ABS and makepkg, and it's brilliant!
Fantastic stuff.
Arch is very well documented. Indeed, all you need is a bit of patience to switch over.
>Microsoft in <10 years?
Offline