On Fri, 19 May 2006 14:17:05 +0200 Thorsten Grothe <[EMAIL PROTECTED]> wrote:
> Am Freitag, 19. Mai 2006 12:21 schrieb [EMAIL PROTECTED]: > > (...) > > > The second case is handled automatically by pacman if your config > > files aren't in NoUpgrade. But a current problem with NoUpgrade makes > > it not safe to remove config files from it, and secondly, NoUpgrade > > extract pacnew files even when there are no differences. So you have > > to diff each pacnew files, realize they are no different, then remove > > these pacnew files. A few times it's ok, but then it gets annoying. > > I proposed a patch here : > > http://www.archlinux.org/pipermail/pacman-dev/2006-May/000321.html > > (sorry about the length of the lines, it's annoying too, not sure how > > I made that) > > Well I understand and I agree fully with you that it's only useful to > produce pacnew files, when the pkg config file has changed. Can you > please tell me where and how to apply the patch? > I would prefer that other people had a look at my patch first (atm, it seems only vmiklos saw it), but well I'm using it since I made it, and it worked fine so far. To apply it, first run abs to get all the PKGBUILDS, then cp -r /var/abs/base/pacman/ /var/abs/local/ copy the patch and the new PKGBUILD to /var/abs/local/pacman/ then makepkg in the pacman directory and finally pacman -U pacman-2.9.8-1.pkg.tar.gz There is a little problem, since the current pacman stores the md5sum of the wrong version of config files in NoUpgrade (local version instead of pkg one), the first time you'll update a package which has config files in NoUpgrade (like filesystem), you'll still get the useless pacnew files. But the following times, you won't get them anymore, unless one of the config files actually gets updated.
PKGBUILD
Description: Binary data
noupgrade.diff
Description: Binary data
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
