When rPath imported RHEL, CentOS, etc., we worked really hard to try to find the missing dependencies not mentioned in RPM. This meant that we had to bootstrap half the OS and use it to find a large set of build requires to find in particular extra Python and Perl dependencies.
Today, the use case of installing packages on a minimal system and expecting things to just work is overall more prevalent on RPM systems than it was ten years ago when much of the install was based on anaconda groups. This means that I expect that RPM dependencies are more complete now in practice than they were when we started writing Conary. Not looking for extra Conary dependencies will make packages smaller and dependency resolution faster, so we're planning to not try to inspect and add all those extra Conary requires over RPM dependencies. We might not even generate any python and perl requires for imported packages. We'll start by whiting out the python and perl requires, but we might speed up import later by turning off calculating them. We'll still have all the normal Provides, so that you can build native Conary packages against the RPMs. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
