Bug#758234: Bug#759260: [PATCH] Remove priority "extra", make all corresponding packages priority "optional"
Russ Allbery <rra@debian.org> writes:
> Ansgar Burchardt <ansgar@debian.org> writes:
>> Stuart Prescott <stuart@debian.org> writes:
>> Related to that: Given d-i/debootstrap are the main users, I think
>> having d-i ignore the priority of library packages already[1] is an
>> indication that allowing packages to depend on library packages with
>> lower priority might not be wrong.
>
>> [1] <https://bugs.debian.org/758234#15>
>
> There's two ways we can solve that problem: either say that priority is
> meaningless for library packages, or be better about automating the change
> in priority. I'd actually prefer the latter, since as a library
> maintainer I'd like to know when my package is being pulled into the
> standard or important set (and particularly if it's pulled into
> required).
It's not only libraries: package A/important could depend on
utility-B. If I don't want A and use debootstrap's --exclude A, I
don't need utility-B either, but will still get it if its priority
is raised to important.
> In some cases, it can change maintenance decisions.
Does this differ much from packages being picked up by other commonly
installed software? Say GNOME starting to depend on my small library
which suddenly raises from ~100 to 50000+ reported installations?
> So, while I don't want anyone to have irritating busy-work to track this
> stuff, I'd really like to trigger some sort of notification to the
> maintainer of the elevated package, at least, and priority seems like a
> reasonable mechanism off of which to trigger. Even if we just automate
> the elevation of the priority in the overrides file along with that mail
> notification.
I admit I'm not a great fan of generating more notifications. As a
maintainer I already filter out most automatically generated mails I
get...
And dak is probably not the right place to manage subscriptions to
certain notifications.
Ansgar
Reply to: