[CentOS-devel] Community build services and EPEL8

Wed Jul 31 10:15:04 UTC 2019
lejeczek <peljasz at yahoo.co.uk>

On 10/07/2019 21:52, Thomas Oulevey wrote:
> Hello folks,
>
> In the planning of next Community build services, a new question came up.
>
> In the past we never allowed EPEL repositories to be used as external
> repositories for SIGs. Doing so, would allow to build against EPEL
> packages and not duplicate the work for maintainers in EPEL/SIGs.
>
> However it would mean also building against a moving target which can
> be difficult if EPEL policies are the same as today.
>
> As EPEL 8 is also in the making it would be good to hear what SIGs
> think about this specific issue.
>
> Let us know !
>
@SIGs, take below as an opinion piece only.

I've chimed in a number of times in various places, probably I'm not the
only one(as non-devel) who suggested - stop with all that SIG nonsense.

Every SIG pretty much, that's what user/admin experience historically
proved, spends time each locked up in own SIG room and there is no world
beyond it. And it works all great, and things there get fixed and
improved, etc.. fantastic if it wasn't for all duplicated packages and
conflicts which for "regular" users is a massive nuisance, and having
multiple repos becomes almost a public enemy no.1.

Have EPEL (which almost everybody begin with, is a must-have) and then
let's say try centos-openstack-some/one, while having R packages, maybe
add octave, nothing too fancy and not too many of it - you will get
conflicts right away. Want something little more fancy - openVswitch -
and more.. hmmm.

And if one has some SIG repos enabled then one hardly ever see EPEL,
which SIGs here seem to be most worried about, releases new versions
which would relieve old packages, it's rather SIGs conflicting packages
which march at faster pace towards newest package version (and which
could go(back) to EPEL)

And we are not even frustrated anymore for in years each who needs extra
bits probably have his/her workarounds worked out and get things which
must have but I, and probably many other "regular" users, will repeat
this again - put it all together and work closer together, find a way
somehow. SIGs have a plenty to offer and what they offer EPEL should not
diminish nor underestimate. If both could work together as one then that
would save time & man-hours for everyone, also would make lives of
end-users/admins everywhere much easier.

many thank & lots love, L.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pEpkey.asc
Type: application/pgp-keys
Size: 1757 bytes
Desc: not available
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20190731/5095de6d/attachment-0008.bin>