cOn 10/20/2016 07:06 AM, Kevin Fenzi wrote: > On Sun, 16 Oct 2016 21:54:44 -0700 > Karsten Wade <kwade@xxxxxxxxxx> wrote: > >> On 10/15/2016 10:43 AM, Kevin Fenzi wrote: >>> On Sat, 15 Oct 2016 07:54:25 +0000 (UTC) >>> john tatt <zikamev@xxxxxxxxx> wrote: >>> >>>> HiSo almost one year ago, some people asked for a 32bits EPEL 7 >>>> repo, as you can see. In last january, the goal was apparently to >>>> bring it just after fixing the ppc64 Do you think it will happen >>>> someday ? >>> >>> I hope so, but it's going to be tricky. There's no RHEL for 32bit, >>> so we would need to use CentOS, but then what do we do at the times >>> rhel updates and CentOS hasn't yet? Perhaps we build against CentOS >>> CI... >> >> I'll go out for a stretch here and ask ... what if we build not only >> against CentOS CI but in the CentOS build system? > > Well, not sure how that would work. > > You mean when you do a 'fedpkg build' it builds the normal epel arches > in the Fedora koji and also fires off a i686 build in the centos build > system? > > If so: > > * We would need to issue certs for every epel maintainer to be able to > build in centos. > * Also the centos build sys would need to allow builds from Fedora pkgs > source. > * Things could get out of sync if the centos build and epel builds one > or the other fails. > * How would maintainers push updates in the centos side? Or would that > just collect the builds and make a single repo/release ? I was mainly proposing a thought experiment, and you're right, there are a lot of bits involved that doesn't make it easy. There may simply be too much inertia until we find the eventual reason to do the work. Part of my thinking is the situation where CentOS SIGs need EPEL packages and (aiui currently) have to import to git.centos.org and build the packages on cbs.centos.org. I'm basically back to being curious on the topic of EPEL & CentOS and how best to interact. Regards, - Karsten -- Karsten Wade Community Infra & Platform (Mgr) Open Source and Standards, @redhatopen @quaid gpg: AD0E0C41
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
