`xbps-query`: Add more fine-grained selectors for listing packages

Aberta
#460 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
c
Domínio
cli

Direção de pesquisa

Start at the xbps-query command entry point and trace how its mutually exclusive MODES are parsed and applied. Review how package states are represented, especially dependency and half-removed states. Done means the supported state selectors and their combinations are clearly defined and xbps-query can list packages matching them.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement

It would be nice to be able to ask xbps-query to only list packages in a certain state, like "is a dep" (the invert of -m) or "is half-removed". For half-removed one could xbps-query -l | grep -e '^hr', but this would not work for selecting dependencies, since there currently is no "state descriptor" for that (I mean like ii).

While selecting e.g. only dependencies may not seem directly useful at first, there will always be corner-cases where such an option will be useful, and I think a great package manager like xbps should support that. To support this, maybe it would be best if xbps-query had a more generic interface, where you could combine several MODES together (or rather, split out some flags which are currently MODES and call them SELECTORS, and then allow them to be combined arbitrarily). Right now the modes for xbps-query are mutually exclusive.

PS: In case this is a welcome addition to xbps-query I'm happy to work on this, but it will take me some time since I'm currently quite busy, and I'm not familiar with the xbps codebase yet.

Linguagem predominante
C
Estrelas
1.2k
Forks
156
Merge médio
1h 39min
PRs com merge (30d)
1

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de void-linux/xbps

Todas as issues de void-linux/xbps

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.