Add context for why yay is asking to choose a provide

[Jguer]

Is your feature request related to a problem? Please describe.

Currently for upgrades yay just asks, for example, when a makedep is necessary (ex: poly-mc):

:: There are 4 providers available for java-environment:
:: Repository extra
    1) jdk-openjdk 2) jdk11-openjdk 3) jdk17-openjdk 4) jdk8-openjdk 

yay should tell you why it's asking you this

Expected output

:: There are 4 providers available for java-environment (required by poly-mc):
:: Repository extra
    1) jdk-openjdk 2) jdk11-openjdk 3) jdk17-openjdk 4) jdk8-openjdk 

[Claudio-code]

Hi,

In this feature, the idea is to show the common dependency that these 4 options have to avoid conflicts?

It's just that for me it wasn't very clear whether it was to show all the dependencies of each option or just to show what they have in common.

[grandchild]

More like show the specific origin of this dependency request. This prompt is shown during installation of another package (or several) that requires this dependency. The options presented may have many dependees in common, but it should show the ones from the current session that triggered this prompt.

[Juneezee]

Not sure if there is a straightforward way to achieve this without libalpm providing more information in struct alpm_question_select_provider_t ¹. I could be wrong here, so please enlighten me on this if someone has an idea.

The goal is to add the (required by X) in our custom question callback. However, struct alpm_question_select_provider_t ¹ only gives us the name of the dependency (in this case java-environment) and the list of providers of the dependency (jdk-openjdk, jdk11-openjdk, jdk17-openjdk, jdk8-openjdk).

yay/pkg/db/ialpm/alpm.go

Lines 163 to 179 in d77dd77

	qp, err := question.QuestionSelectProvider()
	if err != nil {
	return
	}
	if settings.HideMenus {
	return
	}
	size := 0
	_ = qp.Providers(ae.handle).ForEach(func(pkg alpm.IPackage) error {
	size++
	return nil
	})
	str := text.Bold(gotext.Get("There are %d providers available for %s:", size, qp.Dep()))

The fact that setting the custom question callback is part of the initialization (before -Syu is run) also limits the possibilities for workarounds.

yay/pkg/db/ialpm/alpm.go

Line 254 in d77dd77

alpmSetQuestionCallback(alpmHandle, ae.questionCallback())

Footnotes

1. https://man.archlinux.org/man/libalpm_cb.3.en#struct_alpm_question_select_provider_t ↩ ↩²