Maintaining a custom compiled version of glibc in multiple machines

Question

Hi,
I am trying to maintain a custom version of glibc due to the minimum kernel version bump. I have seen the sticky topic in the forum about Updating packages compiled via ABS.
The steps which seem clear to me -
run
abs core/glibc
Copy
/var/abs/core/glibc
to another path and do a couple of changes to PKGBUILD
run from the custom path
makepkg -s
So, creating a custom repo and using that as the top most repo and reinstalling glibc is the way to go when multiple machines are involved ?
When the package is built copy it to another path and run
repo-add
Put the custom repo at the top repo in
/etc/pacman.conf
refresh pacman
pacman -Sy
reinstall glibc using
pacman -S glibc
Is this the way to go ?
cheers !
Last edited by kmganesh (2011-02-16 06:52:01)

Answer 1

kmganesh wrote:So, creating a custom repo and using that as the top most repo and reinstalling glibc is the way to go when multiple machines are involved ?
I would just, after running the abs command and copying the glibc PKGBUILD into a folder in your home directory, run
makepkg -s
in the folder with the PKGBUILD to generate the package and then copy the package onto a USB key to distribute to other machines.
Installing with
pacman -U /path/to/package
Unless you have many machines that you want to install the package on, it is much simpler than creating a repo.
Last edited by andrewthomas (2011-02-15 02:40:52)