[pacman-dev] [PATCH] Group optional dependencies by installation status
Drew DeVault
sircmpwn at gmail.com
Fri Jul 12 01:40:44 EDT 2013
> But that puts the most important uninstalled optdep in the middle of the
> output.
I suppose that's true. From my testing, however, it looks fairly
distinct. Example:
Optional dependencies for cmus
alsa-lib: for ALSA output plugin support [installed]
libao: for AO output plugin support [installed]
libpulse: for PulseAudio output plugin support [installed]
faad2: for AAC input plugin support [installed]
flac: for flac input plugin support [installed]
libmad: for mp3 input plugin support [installed]
libmodplug: for modplug input plugin support [installed]
libmp4v2: for mp4 input plugin support [installed]
libmpcdec: for musepack input plugin support [installed]
libvorbis: for vorbis input plugin support [installed]
wavpack: for wavpack input plugin support [installed]
ffmpeg: for ffmpeg input plugin support
opusfile: for opus input plugin support
What if we moved [installed] to the start of the line, or added a line
between the two groups of packages?
Drew DeVault
On 07/11/2013 11:34 PM, Allan McRae wrote:
> On 12/07/13 13:03, Drew DeVault wrote:
>>> Optional dependencies are (or should be) listed in a PKGBUILD in order
>>> of importance. We previously rejected outputting them in alphabetical
>>> order because of this. Given this patch just groups the installed/not
>>> installed nature of the optdepend, I suppose this is more reasonable,
>>> but I am still reluctant.
>> I can see the concern, but I think the importance of having a package installed disappears once you already have it.
>>> Also, surely uninstalled optdepends are the more important ones and
>>> should be listed first.
>> The idea was getting them closer to the end of the output, where your caret will be prepared to type them in and install.
>>
> But that puts the most important uninstalled optdep in the middle of the
> output.
>
>
>
More information about the pacman-dev
mailing list