Re: git: 2b0da956a025 - main - UPDATING: Add entry regarding glib20 update

From: Colin Percival <cperciva_at_tarsnap.com>
Date: Thu, 03 Apr 2025 23:30:19 UTC
On 4/3/25 16:21, Charlie Li wrote:
> Colin Percival wrote:
>> I really don't think this is an adequate solution.  FreeBSD users expect to be
>> able to launch a clean FreeBSD system with the ports tree installed and run
>>
>> # make -C /usr/ports/devel/glib20 all install
>>
>> and have glib20 built and installed.  It's ok to have special instructions in
>> ports/UPDATING for people updating existing systems, but installing ports on
>> new systems should Just Work without needing this sort of song and dance.
>>
>> Also, this broke this week's 15.x snapshot builds.  For the 4th time.
>>
> Unfortunately upstream have our hands tied and this is the only sane way to do 
> it until introspection is merged into glib proper. It also goes to show how 
> little upstream projects care about avoiding circular dependencies, because 
> their main focus is not necessarily packaging, particularly fully- 
> deterministic building and packaging. Double whammy when nearly a decade of 
> tech debt is involved.
> 
> For additional context to the UPDATING entry beyond upstream's announcement, 
> all the glib introspection files have been built squarely as part of glib and 
> not introspection since glib 2.79/introspection 1.79. Until this update, this 
> situation was masked as glib was at 2.80 but introspection remained at 1.78. 
> The glib introspection files have many direct consumers. In order to build 
> these introspection files, you need introspection itself, which depends on 
> glib. It is not possible to build a stripped/skeleton of either of these.

Why can't the files in the bootstrap packages be installed into a different
directory so they can co-exist with the main packages?

-- 
Colin Percival
FreeBSD Release Engineering Lead & EC2 platform maintainer
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid