I could not use tasksel and install only what I want, but then I have to learn/verify all programs that are required for a functional environment.
Federico Kircheis wrote:
I could not use tasksel and install only what I want, but then I have to
learn/verify all programs that are required for a functional environment.
Don't use a tasksel desktop.
Install one of these metapackages for KDE:
kde-full/stable 5:142 amd64
complete KDE Software Compilation for end users
kde-plasma-desktop/stable 5:142 amd64
KDE Plasma Desktop and minimal set of applications
kde-standard/stable 5:142 amd64
KDE Plasma Desktop and standard set of applications
Or xfce4 to get a working XFCE environment.
There doesn't seem to be a similar metapackage for GNOME, but
perhaps I just missed it.
Any of these should get you to a point where everything is
working.
-dsr-
The only issue I have with tasksel, is that sometimes I wish a more
minimal environment.
The only issue I have with tasksel, is that sometimes I wish a more
minimal environment.
Then don't use tasksel to install package(s).
On 30/06/2025 7:11 pm, Michael Paoli wrote:
And this also holds for metapackages like lxqt.
It still installs a lot of things, so down to lxqt-core.
It still installs some things I've noticed and to not want, so I need to inspect which packages are installed, transitive dependencies included..
I hoped it would have been possible to exlucde dependencies, for examle by prefixing them with "-"; for example:
apt install lxqt -meteo-qt
Federico Kircheis wrote:
On 30/06/2025 7:11 pm, Michael Paoli wrote:
And this also holds for metapackages like lxqt.
It still installs a lot of things, so down to lxqt-core.
It still installs some things I've noticed and to not want, so I need to
inspect which packages are installed, transitive dependencies included..
I hoped it would have been possible to exclude dependencies, for example by >> prefixing them with "-"; for example:
apt install lxqt -meteo-qt
You can postfix "-" to get that behavior.
apt install lxqt meteo-qt-
Also, do you know that the -s switch to apt install will tell
you the whole plan without retrieving or installing the packages?
I'm only aware of '--no-install-recommends' as far as apt goes.
Of course, with a 100 terabyte hard disk, it can seem rather silly.
Oh; i was not aware of that, is it specific for apt?
man apt does not seem to mention it.
I'll try it out.
On Thu 03 Jul 2025 at 18:15:42 (+0200), Federico Kircheis wrote:
On 03/07/2025 5:28 pm, Dan Ritter wrote:
Federico Kircheis wrote:
And this also holds for metapackages like lxqt.
It still installs a lot of things, so down to lxqt-core.
It still installs some things I've noticed and to not want, so I need to >>>> inspect which packages are installed, transitive dependencies included.. >>>>
I hoped it would have been possible to exclude dependencies, for example by
prefixing them with "-"; for example:
No, you don't want to exclude dependencies; doing that will break
packages. That's why they're call dependencies: the package depends
on them being installed.
"apt install lxqt -meteo-qt"
meteo-qt is not a dependency: it's only recommended.
On 03/07/2025 5:51 pm, Greg wrote:
I'm only aware of '--no-install-recommends' as far as apt goes.
Yes, but it has the same issue.
Now many things are missing, and I need to search them out, and
dependencies might change between package releases.
Except that it reverses the logic: --no-install-recommends will
install the packages you ask for, but with minimal extra packages.
When you find that some expected functionality is absent, you
install the package that gives you that functionality, again
with --no-install-recommends to keep your system minimal.
"Now many things are missing":
Well, you can hardly expect the Debian or the DE developers to guess
which functions happen to be the ones that you want.
"and I need to search them out":
Hardly onerous: the package names are likely to be in the Recommends
list of the top-level package you installed.
But if I list all packages, then remove all those that I obviously do
not need, and write a script that install only those, it might "break"
when some packages are updated or new dependencies are added.
With the blacklist approach, I expected it would break only if the
package is now required.
If your "blacklist" system causes breakages, then you can hardly
expect Debian developers to give it any consideration at all.
* downloading and uploading unnecessary data not only takes space on
my drive, but also takes more time and unnecessarily consumes my
traffic plan.
* offsite backups take longer, as verifying they integrity and
restore process
Those are reasons why --no-install-recommends was provided in the
first place.
I'm not necessarily talking about the .deb file by
itself, but also docker images, iso files, virtual machines, and so
on, which are built on top of installed deb packages.
That's a separate concern, and in your hands.
* a system with more dependencies has a higher chance to break than a
system with less dependencies when upgrading components
And I'm sure I can find other reason why avoiding some unnecessary
dependencies has positive side-effects
Again, you're confusing the issue by using the wrong terminology.
APT makes sure that dependencies are satisfied. If an extra dependency
is added (rare), it gets installed.¹ If an extra Recommends is added,
you might not even notice the fact when --no-install-recommends is in
force: and if it were to be undesirable, you wouldn't have to do
anything about eliminating it, like blacklisting it.
¹ apt-get users might require dist-upgrade or --with-new-pkgs when
this happens.
Cheers,
David.
Isn't a recommended package a dependency?
On Fri 04 Jul 2025 at 07:04:32 (+0200), Federico Kircheis wrote:
Excluding two or three packages is much easier, and the suggested
approach of appending a - works perfectly if the package was not
installed.
In which case, I think you should install the equivs package (it's
in every suite) and use it to build your own packages called
libreoffice, etc.
You still need to use one of -s, --simulate, --just-print, --dry-run, --recon, --no-act, in order to see just which package equivalents you
need to build.
Then, in future, you install all your equivalents before you install
the DE itself, and APT/dpkg will see that those _recommendations_ are
already installed. But repeat the -s run after installing your first
set of equivalents in case there are any second-order recommendations.
Cheers,
David.
On 04/07/2025 5:32 pm, David Wright wrote:
On Fri 04 Jul 2025 at 07:04:32 (+0200), Federico Kircheis wrote:
Excluding two or three packages is much easier, and the suggested approach of appending a - works perfectly if the package was not installed.
In which case, I think you should install the equivs package (it's
in every suite) and use it to build your own packages called
libreoffice, etc.
But wouldn't it break if I want to install libreoffice at a later point?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 153:22:22 |
Calls: | 10,383 |
Files: | 14,054 |
Messages: | 6,417,839 |