-
Notifications
You must be signed in to change notification settings - Fork 114
deprecate AUR specific short command options #712
Comments
For the sake of consistency and code simplification, each pacman command that is extended to the AUR should have a direct AUR specific command equivalent:
Man page descriptions should be adjusted accordingly. Note to self: probably a good idea to ask early feedback on forums. Maybe also add a switch to enforce one set of commands instead of allowing both of them at the same time? |
Why don't you use the |
There are a number of reasons that made me choose |
Partially done in f67d43b, bb02226, 9291462 and 60add4b. Still missing:
An equivalent of |
As stated in #744 (comment) it seems odd that
makes sense.
This is what I don't get probably. |
The logic behind this choice is to have similarly names flags as the repo operation. Since While
|
Adjusted in 668393e and 0487a92. This also solves the semantic issue about the selective target implementation, which stays in the code. Todo:
|
Download only / clone only is better left to cower/auracle or any other command line shortcut. |
Pacaur provides two sets of command options, one for AUR only specific actions and another one that extends regular pacman options. While this allows quite a lot of flexibility in the way users can use pacaur, this has however the downside of being quite complex to maintain, not to mention being completely ugly.
Also, the usage of two sets of options that somewhat overlap isn't straightforward to understand, as some options haven't the same meaning in one set or another (f.e.
-y
). To this day, I still see users mixing both sets of options and not understanding how to use pacaur without actually reading the man page.For theses reasons, I'd like to deprecate the AUR specific short command options, and use only "long" options, similarly to what auracle (cower-ng, see #708) does. F.e, instead of using
-s
and--search
, simply implementsearch
as the AUR only option. The pacman extension set should stay unchanged, still allowing the short-s
and long--search
options, to be used with-S
or--sync
.Implementing a temporary "translator" of the old AUR-only options to the new one with a warning message might be needed here.
Also, simplifiying the getops structure would help. See this reference and blog post to handle nested getops in a much readable form.
The text was updated successfully, but these errors were encountered: