-
Notifications
You must be signed in to change notification settings - Fork 631
profiles: mpv: add private-etc #6781
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
base: master
Are you sure you want to change the base?
Conversation
|
ill keep this as draft for now. I will be testing this with private-etc in my mpv.local. |
kmk3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me know if i need to trim private-etc for other profiles which include
mpv.profile such that they do not overlap.
Yes, but please wait for #6783 first, which should make the overlap clearer.
Then, it would be good to use private-etc groups in mpv.profile as well.
See src/include/etc_groups.h for the groups.
Note that everything that is in the default group is automatically included and
can be removed from private-etc.
kmk3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To do:
- Remove redundant
mpvfromprivate-etcin ani-cli.profile - Squash the commits
Please verify is all functions are working and none are broken.
Potential breakage is the main reason why whitelisting commands (such as
private-etc) aren't included in more profiles (especially for profiles that
are enabled in firecfg.config), so it is up to whoever proposes adding them to
investigate that (such as by checking paths and functionality in the man pages
and testing them).
That is, making sure that a profile keeps working is usually much harder than
adding an entry.
Also test hardware acceleration for various GPUs.
It seems currently broken on amd here regardless of this change, apparently due
to disable-common.inc.
When ignoring disable-common.inc it seems to work fine with the changes.
The amd paths seem to already be covered by the current items in @x11.
I have been using this private-etc in my mpv.local for a few days now. I dont seem to have any problems.
Shall I remove disable-common? But that doesn't seem resonable. I unfortunately do not have an AMD device right now. I will test and fix it in 2 weeks when I get access to an AMD machine.
Do I have to squash them? Or will it be take care by squash and merge? If I have to squash them, should I include the ani-cli commit here or create a separate pr after this is merged? |
I'm not an mpv power user so I don't know if there is any relatively common
For this PR, leave it as is. Also note that the entries in this file overall are some of the most important
Commit the removal from ani-cli here, then squash everything. It's good to squash them directly because:
For an squashing example, see: Also, if you tested something specific, it would be helpful to include that in Example: |
add private-etc for mpv
Please verify is all functions are working and none are broken.
Also test hardware acceleration for various GPUs.
Let me know if i need to trim private-etc for other profiles which
include mpv.profilesuch that they do not overlap.Related: #6779