Greg Troxel <gdt%ir.bbn.com@localhost> writes: > I noticed that you aren't proposing to PKGREVISION++. That makes sense, > as this should result in unchanged builds on systems where it built > before. And it's nice that it therefore wouldn't trigger massive > rebuilding. I was wrong on this point - I am told that pbulk (which I have yet to get around to setting up, even though I should) will rebuild if any file in the package has changed. So I think we need to be careful about the benefit to fixing python on mirbsd and the risk to everything else since we're already struggling with an less-than-usually-stable situation in this branch. While this might be irregular, if your'e the one doing mirbsd bulk builds, I don't see any reason for you not have it in your builds (or anyone else). That might be the best compromise, where mirbsd binary packages from you for 2014Q1 will be ok, and the other platforms won't have a build hiccup.
Description: PGP signature