Maintaining a custom compiled version of glibc in multiple machines

kmganesh · 2011-02-15 01:38:02

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)

andrewthomas · 2011-02-15 02:39:26

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)

Allan · 2011-02-15 02:41:54

Or use this repo: http://dev.archlinux.org/~ibiru/openvz/glibc-vps/

schneida · 2011-02-15 10:02:22

Hey that's exactly what I was looking for too. That means it should be possible to install ArchLinux inside my VPS running Virtuozzo with Kernel 2.6.18

kmganesh · 2011-02-16 10:19:58

Thanks for the responses ! Yup using

pacman -U

is the easiest for a single machine. But I am looking at many machines. Also the openvz glibc is a good idea ! but unfortunately I am looking at 2.6.15 with an additional patch https://bugzilla.redhat.com/show_bug.cgi?id=426890

So I guess I am on the right track on this one ?

tomk · 2011-02-16 10:35:26

Yeah, make a repo, nothing to it.

Arch Linux

#1 2011-02-15 01:38:02

Maintaining a custom compiled version of glibc in multiple machines

#2 2011-02-15 02:39:26

Re: Maintaining a custom compiled version of glibc in multiple machines

#3 2011-02-15 02:41:54

Re: Maintaining a custom compiled version of glibc in multiple machines

#4 2011-02-15 10:02:22

Re: Maintaining a custom compiled version of glibc in multiple machines

#5 2011-02-16 10:19:58

Re: Maintaining a custom compiled version of glibc in multiple machines

#6 2011-02-16 10:35:26

Re: Maintaining a custom compiled version of glibc in multiple machines

Board footer