Re: [tlug] Ubuntu 20.04 (Was: Ubuntu 18.04 - changing grub parameters)

["Curt J. Sampson" <cjs@example.com>]

On 2020-05-04 18:03 +0100 (Mon), Schwartz, Fernando G. ]|[ @SCA wrote:

> In my view, the problem is the software environment you create with
> both desktops on the same install. I create different boot entries
> to support various desktops on the same machine. I boot to just one
> desktop environment each time.

I'm a bit mystified as to why this would be a problem. If you have
`/usr/lib/libtk8.5.so` on your disk that shouldn't affect how
`/usr/lib/libtk8.6.so` works. Making this kind of stuff work is
exactly the purpose of distributions.

For what it's worth, my systems have little bits and pieces of all
sorts of desktop environments, with none of them (possibly excepting
Xfce) anywhere near "complete."

This is likely to be true of anybody who uses a wide variety of
programs. Programs written to use the Gnome interface are going to a
fair number of Gnome libraries that will be installed by the
dependency-management system, even if you're using a KDE desktop.

> Why is that? You avoid package dependencies conflicts.

Can you give an example of one of these? I do not see how such a
conflict could arise without the packaging system being pretty clear
that you can have only one or the other of two conflicting packages,
and being clear about what dependences are broken if you remove one or
the other.

The only conflicting pair of packages I've ever seen myself in Debian
is `libssl-dev` versus `libssl1.0-dev`, which affects only local
builds of rather old programs (e.g., Python ≤3.4). `apt` is pretty
clear when you install libssl1.0-dev that it's removing libssl-dev,
and it's pretty clear from `pkg-config --modversion libssl` (the tool
used by build systems to check dependencies) which version is
installed.

cjs
-- 
Curt J. Sampson      <cjs@example.com>      +81 90 7737 2974

To iterate is human, to recurse divine.
    - L Peter Deutsch