[gentoo-catalyst] chost setting for later stages

[gentoo-catalyst] chost setting for later stages

[John Eckhart]

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

I just upgraded from catalyst-2.0.4 to catalyst-2.0.5_pre6 and some of my
existing build scripts broke. One of the scripts broke because chost is now
only valid in stage1 and stage2 builds.

This was introduced in svn ver 1237, the ChangeLog reads:

22 Aug 2007; Andrew Gaffney
<agaffney@gentoo.org>modules/generic_stage_target.py,
modules/stage1_target.py
modules/stage2_target.py
'chost' option is only valid in stage 1/2 specs. have catalyst error
otherwise

How do I chose what chost to build later stages? Is this always set by the
stage2 chost? I was never changing it from stage2 on but previously it was
always set in the spec file.

Thanks,
   John

[-- Attachment #2: Type: text/html, Size: 864 bytes --]

Re: [gentoo-catalyst] chost setting for later stages

[Andrew Gaffney]

John Eckhart wrote:
> I just upgraded from catalyst-2.0.4 to catalyst-2.0.5_pre6 and some of 
> my existing build scripts broke. One of the scripts broke because chost 
> is now only valid in stage1 and stage2 builds.
> 
> This was introduced in svn ver 1237, the ChangeLog reads:
> 
> 22 Aug 2007; Andrew Gaffney <agaffney@gentoo.org 
> <mailto:agaffney@gentoo.org>>
> 
> modules/generic_stage_target.py, modules/stage1_target.py
> modules/stage2_target.py
> 'chost' option is only valid in stage 1/2 specs. have catalyst error 
> otherwise
> 
> How do I chose what chost to build later stages? Is this always set by 
> the stage2 chost? I was never changing it from stage2 on but previously 
> it was always set in the spec file.

Setting chost in stage3.spec is a no-op. Catalyst doesn't do anything with it. I 
added this error so people wouldn't think it was doing something that it wasn't. 
It's a very bad idea to change CHOST between stage 2 and 3. If you think you 
have a reason to do it, you're wrong :)

-- 
Andrew Gaffney                                 http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer             Catalyst/Installer + x86 release coordinator
-- 
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] chost setting for later stages

[John Eckhart]

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]

Thanks for the clarification. Luckily I wasn't changing it, just
(redundantly) specifying it for each run of catalyst. Any chance you could
add a line in the generic spec stating exactly that?

On Dec 17, 2007 12:33 AM, Andrew Gaffney <agaffney@gentoo.org> wrote:

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

[-- Attachment #2: Type: text/html, Size: 2287 bytes --]