[pacman-dev] about pacdiff
I like a lot pacdiff for dealing with pacnew files. I always notice that it miss the grub config because it lies in /boot/ while pacdiff only checks in /etc/ I was curious so I decided to have a look at how many backup config files are not in /etc/ :) $ sh backup.sh > backup-list $ cat backup-list | cut -d'/' -f1 | sort -u boot conf.d home opt srv sysctl.conf usr var Note that we have three crazy files there : empty, conf.d and sysctl.conf. Here are the three problematic files/packages : conf.d/ntp-client.conf / /var/abs/extra/ntp/PKGBUILD /etc/foomatic/filter.conf / /var/abs/testing/foomatic-filters/PKGBUILD sysctl.conf / /var/abs/community/network/ufw/PKGBUILD I should probably report bugs for these, though it was not my original intention. So after this manual filtering, here is the list : boot home opt srv usr var That would considerably slow down pacdiff though so probably not worth it. It is disappointing :)
Xavier wrote:
I like a lot pacdiff for dealing with pacnew files. I always notice that it miss the grub config because it lies in /boot/ while pacdiff only checks in /etc/ I was curious so I decided to have a look at how many backup config files are not in /etc/ :) $ sh backup.sh > backup-list $ cat backup-list | cut -d'/' -f1 | sort -u
boot conf.d home opt srv sysctl.conf usr var
Note that we have three crazy files there : empty, conf.d and sysctl.conf. Here are the three problematic files/packages : conf.d/ntp-client.conf / /var/abs/extra/ntp/PKGBUILD /etc/foomatic/filter.conf / /var/abs/testing/foomatic-filters/PKGBUILD sysctl.conf / /var/abs/community/network/ufw/PKGBUILD
I should probably report bugs for these, though it was not my original intention. So after this manual filtering, here is the list : boot home opt srv usr var
That would considerably slow down pacdiff though so probably not worth it. It is disappointing :)
What about using "locate" to find the files. More general but potentially less slowdown maybe? I guess the user would need to update their locate db though... Allan
On Sat, Feb 14, 2009 at 4:44 PM, Allan McRae <allan@archlinux.org> wrote:
Xavier wrote:
I like a lot pacdiff for dealing with pacnew files. I always notice that it miss the grub config because it lies in /boot/ while pacdiff only checks in /etc/ I was curious so I decided to have a look at how many backup config files are not in /etc/ :) $ sh backup.sh > backup-list $ cat backup-list | cut -d'/' -f1 | sort -u
boot conf.d home opt srv sysctl.conf usr var
Note that we have three crazy files there : empty, conf.d and sysctl.conf. Here are the three problematic files/packages : conf.d/ntp-client.conf / /var/abs/extra/ntp/PKGBUILD /etc/foomatic/filter.conf / /var/abs/testing/foomatic-filters/PKGBUILD sysctl.conf / /var/abs/community/network/ufw/PKGBUILD
I should probably report bugs for these, though it was not my original intention. So after this manual filtering, here is the list : boot home opt srv usr var
That would considerably slow down pacdiff though so probably not worth it. It is disappointing :)
What about using "locate" to find the files. More general but potentially less slowdown maybe? I guess the user would need to update their locate db though...
This would in fact be a ton faster. Perhaps some sort of flag to tell pacdiff to use locate rather than a manual find would be helpful? -Dan
What about using find in /etc but also running a locate? This means that if a user never runs updatedb they still get pacdiff for /etc, but other users can get global pacdiff. On Sat, Feb 14, 2009 at 6:07 PM, Dan McGee <dpmcgee@gmail.com> wrote:
On Sat, Feb 14, 2009 at 4:44 PM, Allan McRae <allan@archlinux.org> wrote:
Xavier wrote:
I like a lot pacdiff for dealing with pacnew files. I always notice that it miss the grub config because it lies in /boot/ while pacdiff only checks in /etc/ I was curious so I decided to have a look at how many backup config files are not in /etc/ :) $ sh backup.sh > backup-list $ cat backup-list | cut -d'/' -f1 | sort -u
boot conf.d home opt srv sysctl.conf usr var
Note that we have three crazy files there : empty, conf.d and sysctl.conf. Here are the three problematic files/packages : conf.d/ntp-client.conf / /var/abs/extra/ntp/PKGBUILD /etc/foomatic/filter.conf / /var/abs/testing/foomatic-filters/PKGBUILD sysctl.conf / /var/abs/community/network/ufw/PKGBUILD
I should probably report bugs for these, though it was not my original intention. So after this manual filtering, here is the list : boot home opt srv usr var
That would considerably slow down pacdiff though so probably not worth it. It is disappointing :)
What about using "locate" to find the files. More general but potentially less slowdown maybe? I guess the user would need to update their locate db though...
This would in fact be a ton faster. Perhaps some sort of flag to tell pacdiff to use locate rather than a manual find would be helpful?
-Dan _______________________________________________ pacman-dev mailing list pacman-dev@archlinux.org http://www.archlinux.org/mailman/listinfo/pacman-dev
On Sun, Feb 15, 2009 at 3:14 PM, Kevin Barry <barryk@gmail.com> wrote:
What about using find in /etc but also running a locate? This means that if a user never runs updatedb they still get pacdiff for /etc, but other users can get global pacdiff.
Your idea appeared appealing at first, but after thinking about it a bit, I changed my mind, I would prefer a flag as Dan suggested. Either the locate db is up-to-date and there is no need to run find, or it's outdated, and it's probably better to not use its results at all because they are probably useless (missing all the new .pac* files, and possibly displaying .pac* files that no longer exist).
On Tue, Feb 17, 2009 at 11:49 AM, Xavier <shiningxc@gmail.com> wrote:
On Sun, Feb 15, 2009 at 3:14 PM, Kevin Barry <barryk@gmail.com> wrote:
What about using find in /etc but also running a locate? This means that if a user never runs updatedb they still get pacdiff for /etc, but other users can get global pacdiff.
Your idea appeared appealing at first, but after thinking about it a bit, I changed my mind, I would prefer a flag as Dan suggested. Either the locate db is up-to-date and there is no need to run find, or it's outdated, and it's probably better to not use its results at all because they are probably useless (missing all the new .pac* files, and possibly displaying .pac* files that no longer exist).
Don't forget about 'locate -e' to cover half of that problem. Obviously patches are welcome for the pacdiff version we ship in contrib/. -Dan
participants (4)
-
Allan McRae
-
Dan McGee
-
Kevin Barry
-
Xavier