Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes?

Liste des GroupesRevenir à cubf misc 
Sujet : Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes?
De : robin.haberkorn (at) *nospam* googlemail.com (Robin Haberkorn)
Groupes : comp.unix.bsd.freebsd.misc
Date : 21. Oct 2024, 18:06:43
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <c09c9091-acd9-820b-eff0-4703cf60215f@googlemail.com>
References : 1 2
User-Agent : Alpine 2.26 (BSF 649 2022-06-02)
On Sat, 19 Oct 2024, John Levine wrote:

The difference between a minor and major version is that minor versions have
the same interfaces.  If the interfaces change, thaat's a major version.
>
That's how it should be, but since the version comes from upstream, you can't be sure about it.

It sounds like the bug is that a breaking change was shipped as a minor version
rather than a major one.
>
I am no longer that sure about it.
I recompiled my VirtualBox port and it did __not__ resolve the issue.
Then I did `pkg install --force qt5-style-plugins`.
That did the job. Obviously the package already was automatically rebuilt, but the version was not bumped, so pkg upgrade wouldn't pick it up automatically. If the rebuild of VirtualBox really was necessary - who knows. At least force-reinstalling it via pkg wasn't enough.
There definitely is some kind of bug.

Date Sujet#  Auteur
19 Oct 24 * [ports] Shouldn't we rebuild all dependant packages whenever a library changes?3Robin Haberkorn
19 Oct 24 `* Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes?2John Levine
21 Oct 24  `- Re: [ports] Shouldn't we rebuild all dependant packages whenever a library changes?1Robin Haberkorn

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal