[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Multilib in Extras repo?

I've looked a bit into preparing the Extras push script for multilib
support. In particular:

 - Copy all noarch packages (considering ExcludeArch) to all
   repositories. This is done already.

 - Find all multicompat -devel binary rpms (considering virtual packages
   and ExcludeArch) and copy them to their multilib capable arch repository,
   e.g. (i386/i586/i686/athlon -> x86_64).

 - Examine the unresolved dependencies of the multicompat packages and
   copy all missing Extras packages into the target repository, too.

For the dep resolving, I've used the Yum back-end's returnPackagesByDep()
method. Although the results look reasonable -- i.e. I see the -devel
packages pull it their mother packages and all their deps in Extras --
I'm not an expert in Yum API programming and have yet to find out what
corner-cases one may need to deal with (Obsoletes? arch/multiarch
package picking extra-burden?) and what other pitfalls may be lurking.

Has anyone else spent thoughts on this? Too late for FE6?

What is the estimated multilib readiness of FE6? Do we expect
many file conflicts (due to arch-specific stuff in generated
headers) or package installer/updater problems (on multilib

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]