Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to whitelist .pacnew files or skip their check #31

Open
drws opened this issue Jul 10, 2017 · 0 comments
Open

Option to whitelist .pacnew files or skip their check #31

drws opened this issue Jul 10, 2017 · 0 comments

Comments

@drws
Copy link

drws commented Jul 10, 2017

Up until now (when I started using pacmatic) I was always manually observing the pacman output and sorted out any configuration differences regularly. There is only one .pacnew file on my machine that I'm deliberately leaving there and that is /etc/pacman.d/mirrorlist.pacnew. The reason is that I manually specify the mirrors I want in /etc/pacman.d/mirrorlist, while the /etc/pacman.d/mirrorlist.pacnew file provides me with the list of all available servers. It also gets automatically updated every time there is a new mirror list, so the only two files remaining even after many mirror list updates are those two files only. As an administrator I only read from the /etc/pacman.d/mirrorlist.pacnew and never write to it. It gets overwritten during the update, so it is always fresh. I only write to the /etc/pacman.d/mirrorlist (thereby manually selecting the servers).

And now for the pacmatic problem. No matter what I do (read "I couldn't find any options/hacks to alter that"), it always asks me about /etc/pacman.d/mirrorlist.pacnew with:

1 .pacnew files found (0 added). Update files now? (Y/n)

And I always have to deny it manually, which is slowing down the workflow and producing unneccessary hiccups. On top of all that, there is also the question what a workout will be needed to convince pacmatic to only update some of the .pacnew files when this situation occurs (I'm only using it for a few days so I didn't stumble upon that situation yet).

In my situation it would be enough to simply disable the .pacnew checking altogether. The pacman output still needs to be observed with or without pacmatic, because pacmatic does not process all of the relevant pacman output (optional dependencies and other post install echoes for example) - and it is practically impossible to do that. So in my case, the main wanted pacmatic functionalities are RSS/mail parsing while I still intend to be involved in the update process.

An alternative to disabling the .pacnew check would be an option to whitelist some .pacnew files so they are skipped during the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant