-
Notifications
You must be signed in to change notification settings - Fork 16
Request for appimaged to omit directory #44
Comments
Relevant code is here so it would be easy to comment out |
Blacklisting doesn't solve the problems of the world. I don't see the reason to monitor |
It appears |
Yes, |
@tresf I would be happy to accept a PR |
Apparently, I'm afraid this may be a |
@tresf one can always create a separate file for these kinds of features. You are hereby invited to send in a patch as proposal, we can then discuss the details. |
I'm not a stakeholder in this feature, it was simply a cosmetic observation while debugging #430. I won't be working on this. |
All right, thanks for the suggestion then, I'll leave this open as a feature proposal. |
Please transfer to the appimaged repo. |
You can send me a list of links of stuff to move via IRC, too, that won't generate as much spam. |
We should follow #30, "What triggers system integration". |
A popular hypervisor "VirtualBox" uses
/opt/VBoxGuestAdditions-X.X.X
on Ubuntu Guests to store information about the VM guest additions, common with each Ubuntu guest running inside a VirtualBox VM. At the time of writing this, this location has several files including 7 subfolders, source code and two desktop files.Running
appimaged
in verbose mode shows many failed attempts to scan and recognize files in this directory.From what I understand this is due to the monitoring of the
/opt
directory. I propose to omit/blacklist directories starting with/opt/VBoxGuestAdditions-
to prevent common unwanted entries in the output log when daemon is initially launched.Does such a blacklisted location already exist within the tool?
The text was updated successfully, but these errors were encountered: