[CentOS-devel] Interested in IA64 build.

Sat Oct 6 13:51:37 UTC 2012
Lamar Owen <lowen at pari.edu>

On Saturday, October 06, 2012 09:11:16 AM Lamar Owen wrote:
> Three more down.... e2fsprogs, util-linux, and w3m all needed the older gettext.  I'll leave it as an exercise for the reader to research if the current versions in 5.8 will build with the gettext in 5.8.... :-)

Also, a note.  While I desire 'clean' building in mock alone, I am not married to that approach.  I have found at least two packages that will not rebuild 'clean' in mock (as I have it set up; YMMV of course, and if I can figure out how to inject the things that will have to be injected for things to build 'clean') but build without issue on my test box that is currently running my rebuild CentOS 5.5.  

These two are metacity and kudzu (both from 5.6).  Since I'm not as interested in fully reproducing the build chain used either by upstream or by the CentOS developers in going from 5.5 to 5.6 as I am in just simply getting up to a reasonably, mostly-compatible, fully-updated 5.8, I am going to 'cheat' a bit and use those packages until I get up to 5.8.  But I highly suspect at this point that 5.8 isn't going to be fully self hosting using mock.  At least not unmodified 1.0.28 mock.  The CentOS-Extras 0.6.13 mock with the right hints (as documented in the changelog and the patch) thrown at it may do that just fine, and so I plan at this point to try the self-hosting build on 5.8 using the older CentOS-Extras mock.  But I need to get to a workable 5.8 first.

And, well, honestly I'm ok with that for my purposes.  If I were building for distribution I would care about that, and I have the logs and the dowrev trees so that I can come back to it later to attempt to build with mock.  But I am on a time budget for this project (well, I'm on two budgets; my time, and the electricity for the build host, which costs roughly 25 cents (US) per hour to operate) and so I need to be efficient, time-wise.  And running rpmbuild as a normal user with a fully-loaded dev environment on a much smaller (and much less expensive to operate) box works for me for now.  I'd like to be a purist; I don't have the luxury to be a purist. :-)

Incidentally, here's a yum trick for you that I've used a few times this morning on my test box.  If you have a set of repos full of more-recently-compiled RPMS (but with the same NEVRA as what is installed) a yum update will not pull them in; to pull them in use:

yum reinstall \*

 (the \* instead of plain * is used so that the shell won't do the globbing, but yum will).

That applies for CentOS 5; CentOS 6 has a yum that includes the 'distrosync' command, but I'm not sure it will pull in all of the new binaries like reinstall will.  

You'll have to do special handling for packages that are allowed to be multiply-installed, like the kernel.