3 ms·
In Arch, there is never a reason to "manually manage a copy outside the package manager". You can and should install everything via PKGBUILDs -- the format isn'
by cookiecaper 17y ago
In Arch, there is never a reason to "manually manage a copy outside the package manager". You can and should install everything via PKGBUILDs -- the format isn't very hard, just keep a template around, fill in the metadata, and make tweaks to the commands to run if necessary. Then everything is always kept in pacman and easy to find and/or remove.
You don't even have to do this; there was a PKGBUILD added to AUR, so all you had to do in this (and most) cases is download the PKGBUILD from AUR or use something like yaourt or clyde that does this automatically.
For me, the problems were fixed with a simple yaourt -S libjpeg6.
And despite Arch's rolling release cycle, I still have much less pain with it than I do with Ubuntu's custom-hybrid-half-versions, based on a release already 4-months-old, with about half of the changes in the newer versions backported, and including handfuls of patches never added upstream. See the Debian SSL fiasco for why this is a bad idea. The system is much feistier than Arch in my experience, even though Arch will occasionally perform upgrades that necessitate lots of rebuilds.
- Legion 17y ago>> "For me, the problems were fixed with a simple yaourt -S libjpeg6." Which makes it all the more disappointing that all I could find were needlessly complex solutions instead. yaourt looks very helpful. Seeing it listed as the 20th "AUR Helper" (http://wiki.archlinux.org/index.php/AUR_Helpers http://wiki.archlinux.org/index.php/AUR_Helpers) didn't exactly make it jump out at me and scream, "this is what you want!"