| 1 |
On Wednesday 21 September 2005 19:52, Chris Gianelloni wrote: |
| 2 |
> On Wed, 2005-09-21 at 17:47 +0100, John Mylchreest wrote: |
| 3 |
> > anyways). After much deliberation I feel the actual best way to deal |
| 4 |
> > with this, is to have an override envvar which will bypass a die, and |
| 5 |
> > simply warn instead. This will mean that those people who |
| 6 |
> > cross-compile regularly, or building stages etc will work fine, and |
| 7 |
> > normal operation would continue to refuse a build if the environment |
| 8 |
> > its building for doesn't seem sane. At the end of the day, the true |
| 9 |
> > root cause of |
| 10 |
> |
| 11 |
> This will not work. Anything environment-wise used to build the stages |
| 12 |
> makes its way *into* the stages. The stages are just builds within a |
| 13 |
> chroot. If I disable it for stage building, then it'll be disabled for |
| 14 |
> anyone that uses those stages by default. |
| 15 |
> |
| 16 |
> The best solution is still a separate check that only throws a warning |
| 17 |
> state, as having a die on the check *is* valid for packages that |
| 18 |
> require a kernel to compile. Also, there's no way in stage building to |
| 19 |
> use a particular environment for only one package, so it would have to |
| 20 |
> be enabled globally. Not something good for packages that really *do* |
| 21 |
> require kernel sources to be present and configured. |
| 22 |
|
| 23 |
Of course this is kind of up to the portage developers, but wouldn't it |
| 24 |
make sense to allow an ebuild to know that it was building a binary |
| 25 |
package or with a ROOT environment. In the case of a binary package |
| 26 |
building these checks could then be postponed to pre_install. |
| 27 |
|
| 28 |
Paul |
| 29 |
|
| 30 |
-- |
| 31 |
Paul de Vrieze |
| 32 |
Gentoo Developer |
| 33 |
Mail: pauldv@g.o |
| 34 |
Homepage: http://www.devrieze.net |
Archives