> ...I would say having SLURM rpms in EPEL could be very helpful for a lot of
> people.
>
> I get that this took you by surprise, but that's not a reason to not have
> them in the repository. I, for one, will happily test if they work for me,
> and if they do, that means that I can stop having to build them. I agree it's
> not hard to do, but if I don't have to do it I'll be very happy about that.
There have been plenty of arguments for why having them in EPEL isn't
necessarily the best option. Many open source products (e.g. Postgres, Docker)
maintain their own YUM repository online -- probably to exercise greater
control over what's published, but also to avoid overlap with mainstream
package repositories. If there is value perceived in having pre-built packages
available, then perhaps the best solution for all parties is to publish the
packages to a unique repository: those who want the pre-built packages
explicitly configure their YUM to pull from that repository, those who have
EPEL configured (which is a LOT of us) don't get overlapping Slurm packages
interfering with their local builds.
::::::::::::::::::::::::::::::::::::::::::::::::::::::
Jeffrey T. Frey, Ph.D.
Systems Programmer V & Cluster Management
IT Research Cyberinfrastructure
& College of Engineering
University of Delaware, Newark DE 19716
Office: (302) 831-6034 Mobile: (302) 419-4976
::::::::::::::::::::::::::::::::::::::::::::::::::::::
