#1072489 apt: what does this recommendation mean? (curl | lynx .. fonts-lato \n | wget)

Package:
apt
Source:
apt
Description:
commandline package manager
Submitter:
наб
Date:
2024-06-02 21:06:06 UTC
Severity:
normal
#1072489#5
Date:
2024-06-02 18:08:35 UTC
From:
To:
Dear Maintainer,

apt build-dep just asked me this in a sid chroot:
-- >8 --
Suggested packages:
  autoconf-archive  cargo-doc  gettext-doc       libssl-doc   | fortran95-compiler  apparmor     libmail-box-perl  libjs-mathjax
  gnu-standards     python3    libasprintf-dev   libtool-doc  gcj-jdk               less         ri                ruby-kramdown-parser-gfm
  autoconf-doc      dh-make    libgettextpo-dev  gfortran     m4-doc                www-browser  ruby-dev          bundler

Recommended packages:
  curl    | lynx       imagemagick  netpbm   libarchive-cpio-perl  libldap-common  publicsuffix      libltdl-dev            zip         fonts-lato
  | wget  ghostscript  libpaper1    psutils  javascript-common     libgpm2         libsasl2-modules  libmail-sendmail-perl  ruby-rouge  rust-llvm

Summary:
  Upgrading: 0, Installing: 88, Removing: 0, Not Upgrading: 0
  Download size: 153 MB
  Space needed: 625 MB / 50.7 GB available
-- >8 --
what does it mean?

I'm assuming the suggestion is "libssl-doc | fortran95-compiler" (odd but maybe).

But what's the recommendations?
"curl | lynx", "fonts-lato | wget"?
I think something like "curl | lynx | wget" makes the most sense,
but in that case why is "fonts-lato" textually before "| wget"?
If the alternatives are vertical too, then how does ghostscript factor
into them?

The build-deps are
  Build-Depends: debhelper, debhelper-compat (= 12), bash-completion, ronn (>= 0.9.0), locales, cargo, pkg-config, libssl-dev,

Best,
наб

#1072489#10
Date:
2024-06-02 20:10:14 UTC
From:
To:
Hi,
so that might be a regression in that sense already.


The reading order for the "new" column view is according to its name:
  111  4    77
  22   55   888
  3    666  9
while the "old" wall-of-text has:
  111 22 3 4
  55 666 77
  888 9

So:

gfortan | fortran95-compiler

curl | wget | lynx

I think the alternatives group might be better of written together and
then the individual columns separated with ~4 spaces like in the
future-suggested "oldname => newname" case.

The individual columns could get quiet big given package names can be
long, but that is a problem for the column display anyhow.


Anyway, I will leave it up to Julian what to do about this as this new
stuff is his baby.


Best regards

David Kalnischkies

#1072489#15
Date:
2024-06-02 21:04:26 UTC
From:
To:
Hi!
hm. this is atrocious to me. is there a layout option that makes the
text go from left to right instead of top to bottom?
i expect to be reading polish or english
(and, indeed, the UI and package names are english),
so the mongolian layout is, well, baffling
you cannot in good conscience try to tell me that anyone in their right
mind will EVER read it like this lol
At the very least the groups should form blocks that only break if
they are taller than the row, rather than anywhere. The fortran
thing is indefensible imo.

If you insist on the mongolian order, then having them form an actual
chain, like
  |curl
  |wget
  |lynx
feels much better than the spaced-out
everything-is-two-cells-apart-so-nothing-is-related soup you get now.
Again, I would like to read the packages in the text order I'm used to,
not in mongolian. This will also instantly clear up any problems that
fall out of an ambiguous spacing because the fallback of "just read it"
will be correct.

Thanks, this was enlightening