Am Montag, 25. September 2017, 02:33:13 CEST schrieb Rich Freeman: > On Sun, Sep 24, 2017 at 2:51 PM, John Blinka <john.bli...@gmail.com> wrote: > >> Is this an officially approved technique?? it is DIRTY. > > > > I imagine that it is sanctioned, otherwise why would there be a > > --changed-deps flag to emerge? Does seem dirty. Glad you asked the > > question. Would love to learn why this is allowed. In my experience, it > > happens quite often. > > Is this recent experience in the main repository? This is something > QA started cracking down on maybe a year ago. It is definitely > problematic, because portage won't pull in the new dependency until > you re-install the package, which means the dependency could get > removed/etc. I'd have to dig up the details around the policy - it > might be allowed in very limited circumstances (there could be reasons > to change a dep that won't actually break anything already installed). > > I ended up putting --changed-deps in my update script because I'd > rather not deal with the bugs this can cause.
I think the debate somewhere ended at "it's maintainer's call, weighing unnecessary rebuilds versus technical correctness". Not sure how time-consuming a qcustomplot is. -- Andreas K. Hüttel dilfri...@gentoo.org Gentoo Linux developer (council, perl, libreoffice)
