You are not logged in.
Hi there,
I've read the excellent wiki and man pages about makepkg, ABS, pacman, etc. but I am wondering about the upgrade question :
1) if I change an ABS, then install it, will my change be preserve next time the package will be upgraded ? For example, I want to provide X support on Vim package. So I modify configure flags "--with-x=no" to "--with-x=yes", then execute makepkg -si. But when Vim will be upgraded, I guess upgrade will replace it by pre-compiled binaries, undoing my modification, am i wrong ?
2) When I build a package from source, for example by performing a makepkg in an ABS or by doing it via an AUR helper, such as yaourt -Sb package :
a) Will the package will be checked for update by yaourt -Syyua --devel ?
b) If so, will the upgrade replace it by a pre-compiled binary version ?
Thank you very much !
Stego++, first general-purpose steganography library ever !
Will use most-used steganographic techniques as modules, with crypto and compression support, and high-quality security features. LGPL.
Release by end 2012. Contact me if you know crypto or stego and would be interested in team working with me.
Offline
1) You're right. You can use the ignorepkg option of pacman.conf to avoid replacing your version of vim. Pacman will tell you when a new version of vim is being ignored, so you can rebuild from abs at that point.
Offline
Hi and thanks for your reply,
So if I get it, if I want to change an ABS or compile from source, new update will still be notificated by pacman, but it will replace the package by pre-compiled binaries, erasing the ASB modification if I made some. So I need to ignore this package, and recompile/modify the new ABS for every update ? Is there a good way to do it automatically ? (without writing my own script)
Thanks
Last edited by ehmicky (2012-02-07 21:32:00)
Stego++, first general-purpose steganography library ever !
Will use most-used steganographic techniques as modules, with crypto and compression support, and high-quality security features. LGPL.
Release by end 2012. Contact me if you know crypto or stego and would be interested in team working with me.
Offline
I haven't really used it but customizepkg from the aur is meant to automate parts of modifying and rebuilding packages.
Offline
Thank you, that's just perfect. :
I'll describe how it solved each of my questions here, because this package has no documentation :
1) By creating a file name "vim" in /etc/customizepkg.d/, pacman will now upgrade vim by source compiling and not pre-compiled binaries installing. By putting some sed-like rules in that file, some modification on the PKGBUILD will be automatically performed each time vim will be upgraded/recompiled from source.
2)a) Yes, but it won't be recompiled from source, unless using solution above.
b) Yes
It's actually very nice, I just have to "touch /etc/customizepkg.d/blender" to compile it from source for every update from now on ![]()
Thanks a lot !
Stego++, first general-purpose steganography library ever !
Will use most-used steganographic techniques as modules, with crypto and compression support, and high-quality security features. LGPL.
Release by end 2012. Contact me if you know crypto or stego and would be interested in team working with me.
Offline