| 1 |
On Tuesday 27 September 2005 22:44, Diego 'Flameeyes' Pettenò wrote: |
| 2 |
> On Tuesday 27 September 2005 14:51, Jason Stubbs wrote: |
| 3 |
> > Variables are _not_ fine. I would think it should be clear to everybody |
| 4 |
> > by now that ebuilds can not pick random things from the computer they are |
| 5 |
> > installing on to define how they will build. |
| 6 |
> |
| 7 |
> If variables are not fine, so can't be find thigns like profile arch, isn't |
| 8 |
> it? But that was a solution chosen for the merge of x86 and amd64... |
| 9 |
> And the same goes with quite everything defined on profile level, like the |
| 10 |
> others. |
| 11 |
|
| 12 |
ARCH has been specifically protected so that whatever the profile sets it what |
| 13 |
the ebuilds see, regardless of the user's environment (except for |
| 14 |
/etc/portage/profile/make.defaults) |
| 15 |
|
| 16 |
> I still think that to users it shouldn't give a damn about ELIBC, USERLAND |
| 17 |
> and KERNEL, as they can just be mislead by thinking that they can change |
| 18 |
> anything about that.. |
| 19 |
|
| 20 |
I'm not suggesting that it should be shown. I'm stating that USE_EXPAND'ed |
| 21 |
variables in general should be shown to the users. Whether there's a profile |
| 22 |
control file to hide specific variables is another question. |
| 23 |
|
| 24 |
> How we can test for and condition dependencies with special profiles others |
| 25 |
> than this way? |
| 26 |
|
| 27 |
Figure out what you want and then get it supported. Right now, the only |
| 28 |
variables that you're guaranteed to see in an ebuild function are ARCH and |
| 29 |
the variables that you find in the ebuild(5) man page. |
| 30 |
|
| 31 |
-- |
| 32 |
Jason Stubbs |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives