Updates to metapackages b-m-all b-m-lite question.

Bearded_Blunder · 2022-02-09 19:48:00

If anyone should happen to apt-get remove <package> from one of the bunsen-meta-all/lite packages, perhaps because they think geany is too heavy for a text editor & don't use it's features, preferring something lighter, or maybe they removed non-free firmware packages because they're a "Libre" devotee/zealot, or just think x package they'll never use on their setup (gparted for those who never plan to adjust their single dedicated hard drive setup, or synaptic for the C-L always wins brigade) the question is:

How will they know if the metapackage gets an update e.g. added or removed package?

As soon as you remove anything from the default dev setup, the metapackage goes away & then apt-get update ceases to tell you...

Perhaps it might be an idea if say @johnraff were to post on the guide thread, or create a new thread with dates & version numbers to notify when there are version bumps? With details of what was added or removed? Maybe a changelog thread?

Anyone who hacks at their setup in any way that removes anything will cease to be notified by apt/apt-get.

While I'm asking questions, anyone using this dev-metapackage.. will they require a reinstall when Beryllium gets released? Or just a change to their sources? I'm not really expecting a commitment on that. Though in an ideal world one would be able to update sources then upgrade && dist-upgrade from one release to the next the same way you can with "pure" Debian.

DeepDayze · 2022-02-09 20:28:36

I've thought when you remove a package that was brought in via a metapackage the metapackage itself also gets removed as the package you removed is one of those that the metapackage in question depends on. You still will get updates to the individual packages left behind via apt. You won't be offered the metapackage itself when updating those packages, but if you do install the metapackage again it will bring back in the missing package(s) that you removed.

Another situation that may occur is a package would get removed if there's some conflict when you update and then the metapackage would also get removed.

Last edited by DeepDayze (2022-02-09 20:30:30)

Bearded_Blunder · 2022-02-09 20:37:03

Exactly, & when a metapackage is being developed, the depends / recommends may change, if it's gone.. you won't know it's updated.. Not a problem in pure Debian Stable, but a potential one in Testing Sid, or Be-dev.

It's for sure a problem if you're playing with sysvinit or runit.. since skipping dbus-user-session & thus not getting the exact metapackage per-se is required in that circumstance.. basically installing all the other "Depends"...

Last edited by Bearded_Blunder (2022-02-09 20:41:30)

DeepDayze · 2022-02-09 20:55:33

Bearded_Blunder wrote:

Exactly, & when a metapackage is being developed, the depends / recommends may change, if it's gone.. you won't know it's updated.. Not a problem in pure Debian Stable, but a potential one in Testing Sid, or Be-dev.
It's for sure a problem if you're playing with sysvinit or runit.. since skipping dbus-user-session & thus not getting the exact metapackage per-se is required in that circumstance.. basically installing all the other "Depends"...

I am sure the metapackages are also updated if the dependencies of said metapackage were to change, such as adding or removing a dependent package...or even if a dependency is renamed.

Bearded_Blunder · 2022-02-09 21:02:12

I've been looking at apt-lisstchanges, or else scripting something that does apt-cache show grep Depends: or apt-ache policy & greps the version comparing to what was originally used, which would solve it for *me* but not anyone who'd run "apt-get remove <random-package>" post install of the meta to save space or resources or just substitute something they liked better...

johnraff · 2022-02-10 00:34:45

Bearded_Blunder wrote:

If anyone should happen to apt-get remove <package> from one of the bunsen-meta-all/lite packages...
How will they know if the metapackage gets an update e.g. added or removed package?
...
As soon as you remove anything from the default dev setup, the metapackage goes away & then apt-get update ceases to tell you...

Correct.

Perhaps it might be an idea if say @johnraff were to post on the guide thread, or create a new thread with dates & version numbers to notify when there are version bumps? With details of what was added or removed? Maybe a changelog thread?

All our packages already have changelogs - it's a standard Debian file - and the metapackage changelogs always (at least since I can remember) show what package dependency changes were made with what package versions. For example, for Beryllium bunsen-meta-all:
https://github.com/BunsenLabs/bunsen-me … /changelog
And you can check the current dependencies of bunsen-meta-all and -light in debian/control:
https://github.com/BunsenLabs/bunsen-me … an/control

I think keeping a forum thread up to date with those changes would be duplication of effort.

...anyone using this dev-metapackage.. will they require a reinstall when Beryllium gets released? Or just a change to their sources?

No need to reinstall - just update the sources and 'apt update'. The installed packages are exactly the same. In fact most of the latest packages are already available on the official BL repo - the experimental repo is a bit ahead with one or two though.

...in an ideal world one would be able to update sources then upgrade && dist-upgrade from one release to the next the same way you can with "pure" Debian.

Yes that would be nice. Though even with pure Debian you still have to make some adjustments - there's usually quite a long upgrading guide published.

#1 2022-02-09 19:48:00

Updates to metapackages b-m-all b-m-lite question.

#2 2022-02-09 20:28:36

Re: Updates to metapackages b-m-all b-m-lite question.

#3 2022-02-09 20:37:03

Re: Updates to metapackages b-m-all b-m-lite question.

#4 2022-02-09 20:55:33

Re: Updates to metapackages b-m-all b-m-lite question.

#5 2022-02-09 21:02:12

Re: Updates to metapackages b-m-all b-m-lite question.

#6 2022-02-10 00:34:45

Re: Updates to metapackages b-m-all b-m-lite question.

Board footer