Hi,
aurweb 4.2.0 will be released soon and one of its new features is an SSH
command to modify package metadata. Currently, only changing keywords is
supported and the syntax (in master) looks as follows:
$ ssh [email protected] config <pkgbase> keywords [...]
One of my concerns with that syntax is that "config" might be a bit too
general. For example, we might want to add commands to change account
settings later. Since it is not part of any public interface yet, this
is the right (and only) time to decide on proper naming.
Other suggestions:
$ ssh [email protected] modify <pkgbase> keywords [...]
$ ssh [email protected] set <pkgbase> keywords [...]
$ ssh [email protected] pkg-config <pkgbase> keywords [...]
$ ssh [email protected] pkg-modify <pkgbase> keywords [...]
$ ssh [email protected] pkg-set <pkgbase> keywords [...]
$ ssh [email protected] pkgbase-config <pkgbase> keywords [...]
$ ssh [email protected] pkgbase-modify <pkgbase> keywords [...]
$ ssh [email protected] pkgbase-set <pkgbase> keywords [...]
$ ssh [email protected] pkg <pkgbase> config keywords [...]
$ ssh [email protected] pkg <pkgbase> modify keywords [...]
$ ssh [email protected] pkg <pkgbase> set keywords [...]
$ ssh [email protected] pkg <pkgbase> set-keywords [...]
$ ssh [email protected] pkgbase <pkgbase> config keywords [...]
$ ssh [email protected] pkgbase <pkgbase> modify keywords [...]
$ ssh [email protected] pkgbase <pkgbase> set keywords [...]
$ ssh [email protected] pkgbase <pkgbase> set-keywords [...]
The first two options also have the disadvantage that they are quite
general. The options including "pkg" (but not "pkgbase") do not have
that problem but they are a bit misleading since those operations are
performed on package bases, not packages (and they require package base
names, not package names). The options including "pkgbase" describe the
semantics very well but they are quite complex and verbose.
I would really like to hear about your opinions/preferences.
Regards,
Lukas
