On Wed, Aug 24, 2016 at 8:44 PM, Jason L Tibbitts III <ti...@math.uh.edu> wrote:
> > To be completely fair, I don't actually know EPEL policy here. The rule > is that you can't conflict with RHEL packages, but SRPMs aren't really > installed the same way as other packages and whether or not they would > install to the same location depends somewhat on your personal .rpmrc. > > As far as I know, this is the adopted policy [1]. Though, I'm not sure if that was ever made official since it's still on a user page. I couldn't find anything that specifically says SRPM names can't be the same and it seems like that is not the process for additional architecture packages. [2] They just use a leading 0 in the release, ex: foobar-1.0-0.1. I'm curious if anyone else has any insight. Maybe it is worth bringing up at a FPC meeting. [1] https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_ Python3#Packaging_Parallel_python3X_stacks [2] https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
_______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
