`xbps-query`: Unify default output formats of package lists
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start with the xbps-query modes described in the issue and the xbps-query(1) documentation, comparing the output behavior of -l, -s, -m, -O, -X, and -x. Review the related issues and pull request before defining the scope. Done should mean the package-listing modes have predictable default and secondary output formats, with the chosen flags documented.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Right now, xbps-query has different default output formats (or even only one output format) for some commands.
Multiple columns:
[root@rootfs /]# xbps-query -l
ii acl-2.3.1_1 Access Control List filesystem support
ii acpid-2.0.33_2 ACPI Daemon (acpid) With Netlink Support
...
[root@rootfs /]# xbps-query -s ab
[*] bash-completion-2.11_2 Programmable completion for the GNU Bash shell
[*] bzip2-1.0.8_1 Freely available, patent free, high-quality data compressor
...
Single column:
[root@rootfs /]# xbps-query -m # same for -O and -X
acpid-2.0.33_2
base-voidstrap-0.11_1
...
[root@rootfs /]# xbps-query -x sway
swaybg>=0
xorg-server-xwayland>=0
...
I think it would be nice if the first two examples (-l and -s) had the same output format. Maybe we can introduce a new "package state descriptor" like nn or -- for "currently not installed" packages? Right now we have, according to xbps-query(1):
ii Package is installed.
uu Package is unpacked but must be configured with xbps-reconfigure(1).
hr Package is half-removed, and can be fully removed with xbps-remove(1).
?? Package state is unknown.
Overall, I think it would be useful to have two different easily reachable output formats (by easily reachable I mean e.g. a simple flag, not a complete --format=... specifier). Often, e.g. when searching packages via -s, additional information like the short description and package version is useful. But often it is also useful to just have a list of package names (without any version string etc.) for batch processing, e.g. saving a list of all manually installed packages to be later fed into xbps-install on another system. I think these are two common scenarios, and having only two default output formats for the various package listing options of xbps-query will make it easier (because more predictable) to use. The flags could be named -v|--verbose (already exists, but maybe it could be used for this) and -q|--quiet. Some modes, like -s, are verbose by default and can be made shorter using -q. And some modes, like -m, are short by default and can be made more verbose using -v.
There was also the (IMO great) idea of adding a --format=... option, however I'm talking about the default output format and perhaps an easily reachable secondary one, for the most common cases.
Related issues/PRs:
- Lenguaje dominante
- C
- Estrellas
- 1.2k
- Forks
- 152
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de void-linux/xbps
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
void-linux/xbps#475 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
void-linux/xbps#701 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
void-linux/xbps#700 ·
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
void-linux/xbps#696 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
void-linux/xbps#695 · 7 comentarios ·
Todos los issues de void-linux/xbps
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
BasedHardware/omi#20271 ·
Los mantenedores suelen responder en 1 día
-
area/ysql kind/bug priority/medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yugabyte/yugabyte-db#34552 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
flux-framework/flux-coral2#509 ·
-
documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
github/copilot-sdk#2804 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Update dbus dependency to ^0.8.0Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
MixinNetwork/flutter-plugins#507 ·