| 1 |
John Eckhart wrote: |
| 2 |
> I just upgraded from catalyst-2.0.4 to catalyst-2.0.5_pre6 and some of |
| 3 |
> my existing build scripts broke. One of the scripts broke because chost |
| 4 |
> is now only valid in stage1 and stage2 builds. |
| 5 |
> |
| 6 |
> This was introduced in svn ver 1237, the ChangeLog reads: |
| 7 |
> |
| 8 |
> 22 Aug 2007; Andrew Gaffney <agaffney@g.o |
| 9 |
> <mailto:agaffney@g.o>> |
| 10 |
> |
| 11 |
> modules/generic_stage_target.py, modules/stage1_target.py |
| 12 |
> modules/stage2_target.py |
| 13 |
> 'chost' option is only valid in stage 1/2 specs. have catalyst error |
| 14 |
> otherwise |
| 15 |
> |
| 16 |
> How do I chose what chost to build later stages? Is this always set by |
| 17 |
> the stage2 chost? I was never changing it from stage2 on but previously |
| 18 |
> it was always set in the spec file. |
| 19 |
|
| 20 |
Setting chost in stage3.spec is a no-op. Catalyst doesn't do anything with it. I |
| 21 |
added this error so people wouldn't think it was doing something that it wasn't. |
| 22 |
It's a very bad idea to change CHOST between stage 2 and 3. If you think you |
| 23 |
have a reason to do it, you're wrong :) |
| 24 |
|
| 25 |
-- |
| 26 |
Andrew Gaffney http://dev.gentoo.org/~agaffney/ |
| 27 |
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator |
| 28 |
-- |
| 29 |
gentoo-catalyst@g.o mailing list |
Archives