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