On Mon, Jan 08, 2018 at 12:09:09PM -0800, Steve Langasek wrote:
Top-posting to just say +1, and that I was going to reply with much the same. I don't even think the requirement for the bootstrap profiles to not functionally change the packages is necessary, but it's the way the folks working on bootstrappability have chosen to do it, so it's their call. But that's definitely not a binding precedent on other build profiles that might be implemented.
How, then, would you tell by looking at the package name+version which kind of package you have? If you're going to change the name or version string anyway, why use some complicated profile system instead of just applying a patch? This seems overly complicated for simple cases and overly fragile for complex cases.
Mike Stone