-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Levi Ramsey wrote:
| I'm not sure if either of those is possible, without breaking Mandrake | on i586 machines (not to mention i686s). It is, it's up to the packager to force '--target i586' when he builds. It is incorrect to force x86 to i586. Actually by the CFLAGS I think i586 is really i686 optimized, but that's beside the point. | As for urpmi, I presume you are talking about rebuilding an RPM and when | the rpm gets upgraded upstream, urpmi --auto-select wants to use the | precompiled version. In that case, the best course is probably to edit | your /etc/urpmi/skip.list and ignore that package, but keep track of the | changelog list, so you know when to download a new version of the SRPM. No, it's more serious than that, in my example I showed the *same version* of the package, just a different arch (i586 instead of athlon). I agree with you that if the package is newer, there is nothing we can do, except that if there is an athlona rch, make it prefer athlon over i586, and if no athlon is available, fallback to i586. But I was complaining that the package versions were exactly the same, this is a more serious problem than upgrades. | | I've begun to develop an interest in adapting urpmi into some sort of | Gentoo-like system. What I could see is creating some sort of | hdlist-like file for the SRPMS directory (listing the rpms that get | built by each SRPM and their provides and so forth). A config file | stating which packages the user wants locally rebuilt as needed would be | useful in that case. I am not familiar with Gentoo. What does it use? Personally, since apt-rpm works, I don't know why Mandrake wanted to develop their own clone of it. Some people still swear by urpmi as the best of these tools, but I don't know how apt handles multiple archs either. - -- Sincerely, David Walluck <[EMAIL PROTECTED]> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9nfxMJB7s/tlHKVIRAr3hAJ90QrFMAh01yQS/lh1OIM3QSArNrgCeNd6E sSLkzFsuLK2jPtEwaBVNQyM= =p4Gw -----END PGP SIGNATURE-----
