On Tue, Oct 29, 2019 at 05:48:14PM +0100, Michał Górny wrote: > On Mon, 2019-10-28 at 10:34 -0500, William Hubbs wrote: > > On Mon, Oct 28, 2019 at 10:18:17AM +1300, Kent Fredric wrote: > > > On Sun, 27 Oct 2019 12:05:02 -0500 > > > William Hubbs <willi...@gentoo.org> wrote: > > > > > > > If a build dep of something changes, the correct response with > > > > --with-bdeps=y is to rebuild everything that depends on the changed dep. > > > > > > Unfortunately, my learned experience of portage is the "correct > > > response" is not something portage wants to do on its own without hand > > > holding. > > > > One thing I've noticed is you say things that portage might do without > > giving any specifics. > > > > Let's go ahead and do the change and file bugs against portage if there > > are issues. > > > > The whole point of PMS/EAPI is that we can rely on package managers > behaving reasonably for any input. Any package managers, in any > version. > > You seem to be suggesting going in the opposite direction of making > newest Portage version handle bad input. Using old version? Tough > luck. Using another package manager? Tough luck. Not fitting > in narrow space of solutions currently hacked around? Tough luck.
No, I'm just saying this: We don't know that there is a portage bug from what I'm reading in this thread. We are talking about possible bugs, but a possible bug isn't a bug. If there is an issue cite it otherwise move on. --with-bdeps=y is the default for a good reason as far as I am aware. William
signature.asc
Description: Digital signature
