On Wed, Mar 13, 2024 at 12:35:14AM -0700, Chandler Sobel-Sorenson wrote: > I concur and also request `--no-all-versions` apply to `apt-cache > policy` command as well. What would this achieve; what is the use case? I literally see no point in having 'policy' limited to a single version (and which one?) given its usually used to show which versions are available from where, how the pin values are for those and which one is considered the candidate as a result of that. > Perhaps, instead, a new option with argument `--versions=N` could be > implemented, allowing a limited number of versions to be returned, with > `--versions=0` or `--versions=none` being the equivalent of > `--no-all-versions`. Uhm… beside that the --no-all-versions flag switches the display from "display all versions" to "display the candidate version only" in e.g. 'show' (and one or the other is the default in apt-cache vs. apt), so the equivalent would be more like '1' … and '0' would display nothing? How would --versions=3 behave through: Assuming I have 5 different versions available in the sources, which of these are displayed and which are not… regardless of the choice, this seems rather unintuitive to discover without many paragraphs of documentation that basically duplicates the code in prose text. Again, what would this achieve and what is the use case for this? Sidenote: If a specific task has no people interested in working on it, its not a good idea to add additional tasks as that is the moral equivalent of saying: "Nobody bought it for 5€, lets ask for 20€"¹. Either create a compelling new task referencing related ones or much better yet do work on it yourself. Its open source after all and nothing will ever get done if everyone hopes someone else will do it. Best regards David Kalnischkies ¹ well, I suppose for e.g. life style products that might work, but somehow I doubt we can "sell" requests as a life style product…
Attachment:
signature.asc
Description: PGP signature