| 1 |
On Sun, Oct 27, 2019 at 12:14:59AM +0100, Michael Everitt wrote: |
| 2 |
> On 26/10/19 23:35, William Hubbs wrote: |
| 3 |
> > On Sat, Oct 26, 2019 at 11:17:18AM +0200, Michał Górny wrote: |
| 4 |
> >> On Sat, 2019-10-26 at 11:14 +0200, Dirkjan Ochtman wrote: |
| 5 |
> >>> On Sat, Oct 26, 2019, 05:59 Kent Fredric <kentnl@g.o> wrote: |
| 6 |
> >>> |
| 7 |
> >>>> On Fri, 25 Oct 2019 15:03:39 -0700 |
| 8 |
> >>>> Georgy Yakovlev <gyakovlev@g.o> wrote: |
| 9 |
> >>>> |
| 10 |
> >>>>> not used anymore |
| 11 |
> >>>>> |
| 12 |
> >>>>> Closes: https://bugs.gentoo.org/695698 |
| 13 |
> >>>>> Signed-off-by: Georgy Yakovlev <gyakovlev@g.o> |
| 14 |
> >>>> Its likely this removal will cause the same kinds of problems faced by |
| 15 |
> >>>> the recent virtual/pam removal, just its more insidious, as the |
| 16 |
> >>>> dependency on the virtual is hidden away inside an eclass. |
| 17 |
> >>>> |
| 18 |
> >>>> But this still means that anything users have already installed will |
| 19 |
> >>>> still depend on this, and without --changed-deps=y, it will break |
| 20 |
> >>>> portage's resolution of anything currently installed using this crate. |
| 21 |
> >>>> |
| 22 |
> >>>> You can work-around this by -r1 bumping everything that used this |
| 23 |
> >>>> eclass .... but this just goes to show why there's policy against |
| 24 |
> >>>> eclasses changing the dependencies of their consumers without any |
| 25 |
> >>>> consumer involvement. |
| 26 |
> >>>> |
| 27 |
> >>> In most if not all cases, this is just a build-time dependency. Do we |
| 28 |
> >>> really have all these problems for build-time only dependencies? |
| 29 |
> >>> |
| 30 |
> >> Yes. Because of --with-bdeps. |
| 31 |
> > I disagree, build-time dependencies can change in place because they |
| 32 |
> > only affect the build. The problem with virtual/pam was that it was a |
| 33 |
> > runtime dependency as well. |
| 34 |
> > |
| 35 |
> > William |
| 36 |
> The problem is that portage defaults to --with-bdeps=y, so any emerging of |
| 37 |
> packages now triggers anything that has a build-dep change, unless, as |
| 38 |
> previously stated, you exclude that case or change the defaults. |
| 39 |
|
| 40 |
Sure, but rebuild changes are exactly what you would want. that's how |
| 41 |
software written in go gets rebuilt for example, which is exactly what |
| 42 |
you want when go is upgraded. |
| 43 |
|
| 44 |
I agree that some rebuilds might be unnecessary, but if you don't like |
| 45 |
compiling/building software Gentoo isn't for you. |
| 46 |
|
| 47 |
William |
Archives