mixer(8): Deprecate some unintuitive control values #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "christos/mixdepr"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is a follow-up to
cc7479d7dc("mixer(8): Improve mute and recsrccontrols"). These deprecated values will be completely removed on
2026-06-15.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
I see that the previous commit in this series was accepted and the manual page does not recommend the short commands anymore. This is fine.
I'd be reluctant to deprecate those short commands though as they don't seem to cause much burden on our side. In fact, removing them will break scripts for no good reason. Especially the values for
mute.Is there a reason why you want those control values gone from mixer(8)?
@0mp wrote in #21 (comment):
This patch is just continuing the deprecation that
cc7479d7dcintroduced 2 years ago. These controls are pointlessly cryptic IMHO. For examplemixer foo.recsrc==is actually a valid control. Keeping them does not really hurt, but I think it's better to keep a clean codebase and interface.As for existing scripts breaking, keeping these deprecation messages for a while should be enough to inform users to update.
Then it might make sense to reflect that in the manual page. I'd remove the cryptic controls from the main chapters. I'd consider mentioning them in the HISTORY section or something to mention that they are deprecated now.
d230ef2783b92cb1fec9@0mp wrote in #21 (comment):
Updated. I don't think keeping a mention in HISTORY is really a good idea. Better to just get rid of them, and only let users who still use those controls know through the deprecation printfs.
The change looks OK.
Reviewed by: 0mp
PS I do not agree with the deprecation but I understand that it has been accepted before by other committers.
b92cb1fec9a28bb575c8