Hi guys,

I've been thinking of how best to get the work that Jeremy's done into trunk.  
I think what I'd prefer to see is the package upgrades handled separately from 
the 64-bit related changes.  That way, I'm hoping it'll be clearer what each 
change entails.  As such, I've started working on a quilt-series of patches 
that aim at closing off the package version bump related tickets in Trac, but 
are based heavily on Jeremy's work.

For example, to upgrade to Glibc-2.6.1, my patch touches packages.ent, 
chapter01/{changelog,whatsnew}.xml as usual.  It also touches 
chapter0{5,6}/{coreutils,gzip}.xml to fix the futimens issue and 
chapter05/gcc-pass2.xml and chapter06/gcc.xml to use --with-arch=i486 so that 
Glibc compiles on my x86 box.

My gcc patch would bump the versions, and change the specs patch to the sed, 
and add the --disable-bootstrap switch.  It wouldn't, however, add the 
--disable-multilib or other multi-arch/64-bit features.  These would be brought 
along in separate commits so they can easily be backed out without having to 
revert the version bump as well.

Does this sound sane to everyone?  If so, I'll endeavour to complete the patch 
series as soon as possible and post it here for review.

Thanks,

Matt.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to