You are not logged in.

#1 2008-04-06 16:37:56

kikinovak
Member
From: Montpezat (South France)
Registered: 2005-12-07
Posts: 93
Website

How do I "preserve" rebuilt packages?

Hi,

The subject says it all. I have an Arch desktop: base system + X11 + XFCE + few apps. Some of the packages are rebuilt. Example: MPlayer is rebuilt with the --disable-gui option, because I only want the browser plugin for Firefox. Now I ponder about what will become of the package.

1) On the local machine, e. g. the one where I actually built the package. I figure out that as soon as a new, more recent version of MPlayer is available, 'pacman -Syu' will squash my custom built version with a "stock" updated version. Now what would be the most "orthodox" policy to handle that?

2) Similarly, let's say I put my own custom-built package on a personal repo on the internet, so I can install it easily on several machines. I *think* (correct me if I'm wrong) that if I put my own repo on top of the repo list, MPlayer just won't be updated if there's a new version available. So in that case, I have to check (manually) if there's an update available and rebuild it eventually.

Any suggestions?

Closing remark: I'm a 100% GNU/Linux user since 2001 (mostly Slackware, Debian and CentOS). I'm using Linux at home and at work. Been fiddling with Arch for the last few days, and I can only say: wow! I love it!


Dyslexics have more fnu.

Offline

#2 2008-04-06 16:42:46

WhiteMagic
Member
Registered: 2007-03-01
Posts: 85

Re: How do I "preserve" rebuilt packages?

Regarding 1) you could simply edit the file /etc/pacman.conf and add/edit/append the following line:

IgnorePkg = mplayer

This should prevent pacman from updating the package via pacman -Su (you might find some other hints in man pacman.conf).

Offline

#3 2008-04-06 23:36:44

mcmillan
Member
Registered: 2006-04-06
Posts: 665

Re: How do I "preserve" rebuilt packages?

#1 WhiteMagic's suggestion is probably the best way to deal with it. Another way would be to build your package with a different name. You can get it to still satisfy dependencies if you include a line in the PKGBUILD:

provides=("mplayer=${pkgver}")

And you probably also want

conflicts=('mplayer')

so it doesn't mess things because it has the same files/
#2 sounds correct to me.

Last edited by mcmillan (2008-04-06 23:37:08)

Offline

#4 2008-04-07 03:47:04

kikinovak
Member
From: Montpezat (South France)
Registered: 2005-12-07
Posts: 93
Website

Re: How do I "preserve" rebuilt packages?

The second solution sounds interesting. Now if I name the package mplayer-nogui, it won't get squashed by 'pacman -Syu' in case an update for mplayer is available. Correct me if I'm wrong.


Dyslexics have more fnu.

Offline

#5 2008-04-12 00:26:05

Misery
Member
Registered: 2008-04-10
Posts: 41

Re: How do I "preserve" rebuilt packages?

You could use "customizepkg" [1] for that. You can create some rules [2] with it and if you upgrade with yaourt like "yaourt -Syu" it will automatically rebuild "mplayer" with your changes from the new source.

[1] http://aur.archlinux.org/packages.php?ID=10314

[2]
remove#depends#smbclient
remove#depends#jack-audio-connection-kit
remove#depends#gtk2
remove#depends#lirc-utils
remove#global#--enable-runtime-cpudetection
replace#global#--language=all#--language=de
replace#global#--enable-gui#--disable-gui

Last edited by Misery (2008-04-12 00:26:42)

Offline

Board footer

Powered by FluxBB