[Bug 285253] devel/dbus: upgrade without bumping dependent ports breaks ... everything

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 08 Mar 2025 18:34:03 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285253

--- Comment #11 from Chad Jacob Milios <milios@ccsys.com> ---
(In reply to Gleb Popov from comment #7)

thank you for elaborating. that aligns with my current understanding :phew: lol

> First, bumps wouldn't help this issue. The service wouldn't be restarted anyways. .... A user should understand what he's updating and how to do that safely.

i *now* understand *this* particular occurrence (the PR) as per your comment #4
turned out to not even be a valid case of the bumps lol

> the pkg tool itself is also somewhat low-level. And using it again requires a user to be the "power user".

yeah i definitely don't want our base tools to start doing all the "magic" that
Ubuntu et al are doing to a live system to "assist" the sysadmin with their
upgrades (and general work). i actually would prefer to shoot my own foot
occasionally. higher level tools and/or more commands/functionality being added
to pkg/ports are great. i enjoy freebsd because fewer interfaces break in a
decade than seem to break every year on the linux platforms i work with

> Just why you're reimplementing Poudriere?

we've been using and updating this system since long before Poudriere was
conceived and for our workflow it's better suited. anything we'd want of
Poudriere it already did and then some. it'd be trivial to implement a change
like the functionality we initially spoke of; in fact it's there already i'd
simply have a policy decision to make regarding how cautious (DSO abi
major+minor on just LIB_DEPENDS) and how deep (1 level).

i, like many im sure, am just made complacent by the current modality of
counting on PKGNAME to change but if i see a memo that's really stopping i'll
gladly adjust my routine. sounds like thatll be further away than i initially
interpreted your comment #2 to mean

-- 
You are receiving this mail because:
You are the assignee for the bug.