-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add IgnorePath
defaults for new configurations/packages
#37
Comments
Thanks for filing this. It has been on my list of things for a while. Excerpt from my TODO file:
That should already be excluded by default ( |
I have been using aconfmgr on my workstation recently and really loving it - thank you for working on this @CyberShadow! Here is my ignore list - this might be too broad for some people, but I think might be a useful starting place for people who want a more manageable list of configs starting out:
|
How certain are you that everything in '/usr/share/*' is safe to ignore? I was expecting these to be installed by postinstall/preinstall hooks, but grepping around a bit in /var/abs looks like many package include fonts and icons as normal (tracked) files in the package, and i couldn't find a reference to the gschemas.compiled. Checking for some "really popular ones" that aconfmgr took as stray, like |
Well, there is a comment at the top that says |
IgnorePath
defaults for new configurations/packages
Ah, good point. I wrote a quick script to confirm that indeed the majority of the files are autogenerated. A bunch are not, but are owned by a package. and a couple of them don't have the header and are not package owned. But inspecting them reveals they're either binary files or probably autogenerated in which case i would consider it a bug that they don't have the header.
|
Are there any improvements on this request yet? |
2024, Any Idea of what I should ignore? |
Hey Cybershadow,
This is basically a request for sane defaults or documentation on a default suggested IgnorePath list.
For example it is safe to assume that any Arch user will want to ignore /var/log from the scans and I can't imagine anyone wanting to include the pacman cache either.
I have only just started to test aconfmgr but my list is already 21 lines long and I don't think I have excluded everything that needs excluding as yet (it is still scanning).
Thanks,
Alan Jenkins
The text was updated successfully, but these errors were encountered: