> Just wondering : if people would like to consume epel pkgs, but still
> want to cherry-pick which version of pkgs they need/want : what about :
> - creating tag/targets for epel (but not building *any* pkg there)
> - rsync (without any delete) epel
> - use "koji import" to import all epel pkgs, and also new versions when
> new pkgs appear
>
> That would mean : nothing to build on cbs, and people can just "cbs
> tag-build" existing imported pkgs.
>
> Would that work for everybody ?
The problem is that there may be build/link issues when a new version of
a package gets introduced in EPEL. Already build binaries may not be
able to function with the updated package from EPEL, it may be required
to rebuild some packages in the SIG.
For Gluster we have at least one of such a candidate (userspace-rcu). In
order to prevent these issues, the old userspace-rcu needs to be
provided by some repository too. Not sure if we should tag a build of an
EPEL package into a repository provided by the SIG...
There are very few dependencies that Gluster has with EPEL. I am fine
with rebuilding those few packages in order to keep things simple and
prevent unexpected issues.
I am laughing at this because one of the reasons why things like gluster and openstack are no longer available in EPEL was because they were moving too fast for users and we were getting complaints about those package changes being broken. And then we cause the same issue to gluster/openstack users because things in EPEL moved too quickly.
That said, I agree it is a problem and I am not saying people HAVE to use EPEL directly. I just want to make it possible that
1. You can use EPEL if you want, and not use EPEL if you want.
2. You can import src.rpm/spec files into CBS from EPEL as easily as possible.
3. You can get whatever fixes into EPEL so people who are doing things like mixing gluster and epel or openstack and epel aren't broken.
If those goals are useful and we can make that happen.. I will do what I can to make it happen.
Niels
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel