I think it will use the current style. Also using config.site for uclibc 
CHOSTS's etc, so Glibc builders on a Glibc host don't cross compile anything. 
The stable branch would branch from current unstable, but a few of the 
svn-20060717 packages and command will be reverted. I'd like to keep stable 
and unstable books as similar as possible. I don't think JHALFS will need any 
significant changes.

robert

On Friday 29 September 2006 17:00, George Boudreau wrote:
> Robert,
>
>    When your create the 'stable' branch using SVN-20060717 will you be
> keeping the build format. ie. separate binutil/gcc or are you going to
> use the embryo/coccoon/butterfly style from the trunk.
>
>    If the stable branch uses the older build style I will have create
> jhalfs code for the stable branch. It is not a problem, it would be a
> one shot coding job.
>
>   G.

Attachment: pgpsjPKTVHV9z.pgp
Description: PGP signature

-- 
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
  • HLFS & JHALFS George Boudreau
    • Re: HLFS & JHALFS Robert Connolly

Reply via email to