On Fri, 19 May 2006 08:32:32 +0200 Thorsten Grothe <[EMAIL PROTECTED]> wrote:
> Am Donnerstag, 18. Mai 2006 09:07 schrieb Mac!eKs: > > > > > a semi-automatic solution is to use dotpac, you can find it in AUR: > > Name: dotpac 0.2-1 > > Description: This little bash script helps you getting rid > > of your /e > > tc/*.pac* files. > > This works fine thank you. Maybe this is a philosophic question: I'm not > sure what to do now. I got a couple of pacnew files and dotpac shows me > a lot some differences between old and new files. I'm not very familar > with them. So is it save to ignore the differences and delete them? > I think this question goes in another direction: Is it possible and save > to upgrade Arch via pacman or is it better to install every new version > of Arch? > There are 2 cases : - you have edited the current config file, so just make the same changes to the pacnew one, then replace the config file with the new one. - you didn't edit the current config file, so you can safely overwrite it with the pacnew one. 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) XC _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
