On 12/25/19 10:49 AM, Franco Fichtner wrote: > >> On 25. Dec 2019, at 12:59 PM, D'Arcy Cain <[email protected]> wrote: >> >> On 12/24/19 5:56 PM, w.schwarzenfeld wrote: >>> At least a workaround (maybe the sollutiion): >>> >>> >>> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209881&action=diff >> >> Another workaround if you don't want to modify files in the repo is to >> simply go into the problem folder, /usr/ports/graphics/graphene in the >> OP's case, and run "make install" before returning to the original >> build. You may have to do it multiple times for different packages though. > > While Poudriere is nice and all and does this automagically it is a major > annoyance trending lately that you cannot build ports without these silly > build errors. If USES= python:XXXX is used it doesn't mean ports should > just barf all over users with these non-errors when they don't build deps > with that particular version that one didn't even specify for the deps. > > It seems like USES enforces this recursively but should not as witnessed > by this "workaround". There's still a relevant DEFAULT_VERSIONS entry > but it is happily ignored. > > If all users need to use Poudriere just to have a chance at building > ports we're at the point where Poudriere itself is becoming problematic > for port framework quality, something that always seemed to linger in > the background for the last couple of years and now it's finally here. > > And yes, lang/rust was one recent example that has python:3.3+ now and > fails to build somewhere down the dependency chain. > > > Cheers, > Franco
I agree with Franco. I am surprised that this error has been known for so long, and not fixed, when at least one effective solution exists. Stephen _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
