You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rationale: I am querying the installed versions of all mate-desktop components.
Usually I use --version; or I check the .pc file. mate-notification-properties comes
without .pc file, and the binary that is installed does not honour --version; instead
it just starts a GUI, which is nice, but I'd like to have a --version flag if that is
possible. Unfortunately I don't know C well enough to propose code addition for
honouring --version or any other flag. (A .pc file could be installed instead, or in
addition to it; I have no preference here. My objective is solely to obtain the
version String, no matter which way to go about it.)
contains the version String, so I can parse it. But perhaps having the binary report
--version may be cleaner than this approach. At any rate, thank you for reading this
issue request.
The text was updated successfully, but these errors were encountered:
Could we support this option:
Which would yield the String:
right now?
Rationale: I am querying the installed versions of all mate-desktop components.
Usually I use --version; or I check the .pc file. mate-notification-properties comes
without .pc file, and the binary that is installed does not honour --version; instead
it just starts a GUI, which is nice, but I'd like to have a --version flag if that is
possible. Unfortunately I don't know C well enough to propose code addition for
honouring --version or any other flag. (A .pc file could be installed instead, or in
addition to it; I have no preference here. My objective is solely to obtain the
version String, no matter which way to go about it.)
Note: interestingly the file:
contains the version String, so I can parse it. But perhaps having the binary report
--version may be cleaner than this approach. At any rate, thank you for reading this
issue request.
The text was updated successfully, but these errors were encountered: