| 1 |
On 10-02-2006 00:38:47 +0000, Ciaran McCreesh wrote: |
| 2 |
> On Thu, 09 Feb 2006 19:26:11 -0500 Alec Warner <antarus@g.o> |
| 3 |
> wrote: |
| 4 |
> > Assuming the CHOST variable is 'safe' is not a good thing, users can |
| 5 |
> > over-ride this variable. Can you specify some behavior when it's set |
| 6 |
> > to something bogus ( invalid form ) or something thats not in the |
| 7 |
> > mapping? |
| 8 |
> |
| 9 |
> Users that override CHOST to something outside of one of the safe forms |
| 10 |
> (or at all, on many archs) won't be able to compile anything anyway. |
| 11 |
|
| 12 |
On 10-02-2006 01:38:54 +0100, Diego 'Flameeyes' Petten wrote: |
| 13 |
> Users can change CHOST, but if they do in the wrong way, they can do way more |
| 14 |
> damage than just this. |
| 15 |
|
| 16 |
Indeed. But this reason is worth a note in the GLEP. I'll add it as |
| 17 |
grounding why we assume CHOST is 'safe'. |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Fabian Groffen |
| 22 |
Gentoo/Alt |
| 23 |
-- |
| 24 |
gentoo-dev@g.o mailing list |
Archives