On Mon, Jan 22, 2018 at 11:57 AM, Michał Górny <mgo...@gentoo.org> wrote: > W dniu nie, 21.01.2018 o godzinie 20∶24 -0800, użytkownik Zac Medico > >> Should we tell users to use the emerge --changed-deps=y option? Maybe >> make --changed-deps=y a default setting? > > No. The idea is that not all dependency changes need to be explicitly > propagated. The developer needs to weigh the pros and cons > of propagating the change, and choose wisely. There is really no need to > enforce a lot of unnecessarily frequent rebuilds because of minor > dependency correction that doesn't really apply to the user. >
I tend to agree, but one of the complications here is the break in time between the error and the consequences. If a dev commits a change and in six hours users start reporting breakage, then the error is easily identified and fixed, and the dev tends to learn not to do that again. If a dev commits a change, and in 12 months users get weird breakage when building or using other packages, then everybody runs around in circles, the error is at least somewhat painful to identify, and the dev has probably made the same error 5 other times since, if they're even still maintaining that package. A repoman warning would definitely help here. Forcing unnecessary rebuilds isn't really the ideal solution, though I'll admit I've been doing this for a while now since things were getting painful a while back. -- Rich
