using same makepkg after every update?

gav616 · 2008-09-08 20:39:59

Say if I tweak a makepkg file for a package in AUR, after an update how do i make it use my tweaked one again (instead of retrieving the default one every-time)

Allan · 2008-09-08 22:01:43

I have no idea about what you mean here... Are you adjusting the PKGBUILD from an AUR package?

gav616 · 2008-09-08 23:36:36

yeah, (ill go into abit more detail)

i've placed the pkgbuild file from a aur package in my home dir (~/abs/package),
then i'm tweaking the pkgbuild file and compile and installing it from the home dir (yaourt -U 'package')

but when i go to update and it finds an update for this package how to i make it use my tweaked 'pkgbuild', beacuse when i go to edit its the default one from aur not mine.

Profjim · 2008-09-08 23:37:16

One way to do this is to keep your tweaked PKGBUILD around. When you see a new version appear on AUR, check out the new version's PKGBUILD. If the only change is a bump in the version number (and a corresponding change of the md5sums), then just bump the version number on your tweaked PKGBUILD and either update (more secure) or delete (not secure at all) the md5sums on your tweaked PKGBUILD. Then makepkg in the directory containing your tweaked PKGBUILD and it will build the new version, retaining your tweaks.

There's a second, more automatic way to do this, which may be more what you're looking for. This is to use customizepkg (it's on AUR). You have to translate your tweaks into commands for customizepkg, and this tool is poorly documented. (At least, I haven't found any serious documentation. I "get" what one needs to do to make it work, though.) With this tool, you can for example, tell yaourt to check updates against AUR as well as against the official repositories. If yaourt finds and wants to install an update from AUR, it will first check if there are any customizing commands in /etc/customizepkg.d/ for this package. If there are, it will apply them to the PKGBUILD it downloads from AUR. Yaourt prompts you to inspect the PKGBUILD before installing anyway, so you'll have the chance to see if anything went wrong applying your customizations.

This second strategy takes more work specifying your customizations. However, once you've got it set yp for a particular package, updates thereafter are a breeze---at least, until the PKGBUILD changes in more radical ways.

gav616 · 2008-09-09 10:43:57

Profjim wrote:

One way to do this is to keep your tweaked PKGBUILD around. When you see a new version appear on AUR, check out the new version's PKGBUILD. If the only change is a bump in the version number (and a corresponding change of the md5sums), then just bump the version number on your tweaked PKGBUILD and either update (more secure) or delete (not secure at all) the md5sums on your tweaked PKGBUILD. Then makepkg in the directory containing your tweaked PKGBUILD and it will build the new version, retaining your tweaks.
There's a second, more automatic way to do this, which may be more what you're looking for. This is to use customizepkg (it's on AUR). You have to translate your tweaks into commands for customizepkg, and this tool is poorly documented. (At least, I haven't found any serious documentation. I "get" what one needs to do to make it work, though.) With this tool, you can for example, tell yaourt to check updates against AUR as well as against the official repositories. If yaourt finds and wants to install an update from AUR, it will first check if there are any customizing commands in /etc/customizepkg.d/ for this package. If there are, it will apply them to the PKGBUILD it downloads from AUR. Yaourt prompts you to inspect the PKGBUILD before installing anyway, so you'll have the chance to see if anything went wrong applying your customizations.
This second strategy takes more work specifying your customizations. However, once you've got it set yp for a particular package, updates thereafter are a breeze---at least, until the PKGBUILD changes in more radical ways.

thank you, atm i do do that first option, i keep the tweaked file and when every i feel like compiling the new svn i just copy/paste/compile/install,

will also have a good look at customizepkg, finding out how it works will be fun

toofishes · 2008-09-09 13:35:41

Maybe you should start with understanding makepkg (try the man page and actually building some packages with it) before trying to use these helper programs.

Arch Linux

#1 2008-09-08 20:39:59

using same makepkg after every update?

#2 2008-09-08 22:01:43

Re: using same makepkg after every update?

#3 2008-09-08 23:36:36

Re: using same makepkg after every update?

#4 2008-09-08 23:37:16

Re: using same makepkg after every update?

#5 2008-09-09 10:43:57

Re: using same makepkg after every update?

#6 2008-09-09 13:35:41

Re: using same makepkg after every update?

Board footer