Like I said, it obviously can only track files installed by the package, if the conf was generated by the executable after, or if you created it, the package system cannot know about it.
Also, you’re still using -S wrong. It takes a file path as argument, not a package name. And does the opposite of -L by showing you which installed package, if any, owns an existing file.
this command didn’t really do what I wanted it to do then
I just want to do something like find {package name} | grep "config.conf" or something like that. I normally know what the program is called, I just don’t know where it is located.
Like I said, it obviously can only track files installed by the package, if the conf was generated by the executable after, or if you created it, the package system cannot know about it.
Also, you’re still using
-Swrong. It takes a file path as argument, not a package name. And does the opposite of-Lby showing you which installed package, if any, owns an existing file.And like I said
I just want to do something like
find {package name} | grep "config.conf"or something like that. I normally know what the program is called, I just don’t know where it is located.No it does exactly that. The issue is that the config you are looking at was not created by a package.