View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0016811||CentOS-8||_unreleased_devel_pkgs||public||2019-12-09 20:43||2020-03-18 22:57|
|Target Version||Fixed in Version|
|Summary||0016811: package libepubgen-devel is omitted from the CentOS-Stream repositories|
|Description||The libepubgen source RPM from the Vault builds both a base package and a development package, but the development package is not available from and of the CentOS 8 repositories. I would expect to find it in PowerTools and Stream-PowerTools.|
|Steps To Reproduce||Execute the command|
dnf --enablerepo=Stream-BaseOS,Stream-AppStream,Stream-PowerTools install libepubgen-devel
There is also a -doc package that seems not to be available, either. Only the base libepubgen package is available.
|Tags||No tags attached.|
|Can you tell us a little more about what libepubgen-devel is used for? Is this blocking a build, and if so what package?|
libepubgen-devel contains components required to build programs that use libepubgen, a library for generating EPUB documents (which itself is packaged separately, per RedHat / CentOS standard practice). Without those components, one can still install and use existing packages that depend on libepubgen, but one cannot (re)build such packages, build new ones, or build local custom software that uses libepubgen.
I haven't a complete list of CentOS packages that require libepubgen, but libreoffice-emailmerge is among them. This CentOS package and others like it cannot be built without components that are not presently available from the CentOS repositories. Personally, however, I am more interested in building libepubgen-based software that is not already packaged for CentOS, and this also is impossible without components that are not available from CentOS. Once built, however, such software can _run_ on CentOS with only official packages.
Frankly, I didn't realize that there was anything controversial about the proposition that CentOS should package and distribute the development components for all the libraries it packages and distributes. Especially when the packages are already being produced by the build process, as can be seen from the relevant source RPM. To the best of my knowledge, this has been standard practice for as long has development components have been packaged separately.
|2019-12-09 20:43||jcbollinger||New Issue|
|2019-12-16 21:35||toracat||Relationship added||related to 0016492|
|2020-02-10 19:25||toracat||Status||new => acknowledged|
|2020-02-12 15:38||bstinson||Status||acknowledged => feedback|
|2020-02-12 15:38||bstinson||Note Added: 0036271|
|2020-02-13 16:14||jcbollinger||Note Added: 0036286|
|2020-02-13 16:14||jcbollinger||Status||feedback => assigned|
|2020-03-18 22:57||toracat||Category||-OTHER => _unreleased_devel_pkgs|