I’m trying to use OBS to build a bunch of packages, and am expanding from just openSuSE repositories to CentOS 5 repositories. Unfortunately some of the dependency packages that I need are in the Fedora EPEL repository and not the standard CentOS 5 repositories, which is causing build failures. So, I have two questions:
Is there a way to tell OBS to use an external repository like EPEL? I do not believe there are any license issues with the EPEL packages.
If the answer to #1 is no, is there a way to tell an OBS package to use another OBS repository to search for packages? So, if I create a sub-project of my home project specifically for epel packages that I pull in and compile, how do I tell the OBS package (in a different subproject) to use that package/repo for build dependencies?
You only have the base repositories available. But you can rebuild on your project EPEL packages, you can even make a package from an SRPM on the internet. EPEL SRPMs are available, so use them as source for your package.
You can set the package repos to publish or not the package… it’s really up to you how you do it
I think it’s better if you rebuild the SRPM… people will be able to get the dependencies from your repo without having EPEL installed… It’s probably nicer for your users to be able to install the package and deps than having a dependency on a foreign repository…
I do have the same problem, but my package is in the official Mandriva:2011:Contrib repository (which everyone uses) - which is not available in the OpenSuSe Build System. Why should I create another copy of the source and risk it to offer old sources (with possible security flaws that already have been fixed in the official repository). This can’t be the correct way!