Mike Frysinger wrote: > On Thursday 01 February 2007, Alec Warner wrote: >> But at that point the manager has little or no control over the package, >> hell you can move the savedconfigs out of /etc/portage/ cause they have >> nothing to do with it at all. >> >> You can't do use-deps with this, because you can't effectively enumerate >> what a savedconfig build will actually build with (assumining >> savedconfig is enabled for that package) since the manager's choices >> will just get over-ridden. The PM would be required to essentially scan >> the savedconfig and parse them into an internal package config state. >> And from a PM point of view that blows ;) > > how does any of this ever really matter in the bigger scheme ? the point is > that you can never effectively enumerate the options to the pm, so just stop > getting in the user's way and let them fully customize the package > -mike
Because then you get fun things like package.provided where people inject a randomly configured package that fails PM tests (aka built_with_use). You'd have to have some sort of tautology that says provided packages (and crazyconfig packages) always pass any checks (such as built_with_use, but could be other checks as well) and then just fail during build if they don't. -- gentoo-dev@gentoo.org mailing list
