On Wed, Nov 6, 2019, at 14:34, Leon Fauster via CentOS-devel wrote:
Am 06.11.19 um 18:35 schrieb Brian Stinson:
<snip> > > The problems we need to solve if we decide to ship these packages somewhere in > a CentOS artifact: > > - Communicate that these packages are provided as-is and are not meant for > runtime dependencies
Is a separate repo with a expressive name and corresponding wiki page not enough (like CR)?
- Provide the packages in a form that is consumable for individuals and the EPEL community
I'd like to propose that we create a separate repository, disabled by default that is composed of the -devel packages that we care about, bundled in a module.\
Why modules? What problem gets addressed? Why not just dropping the unshipped build output into a separate repo?
-- Leon _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Any unshipped package that is the member of a module is part of a blacklist in the distro repodata. If we don't bundle these into a module, there's no way for your workstation to know that this package is intended to be installable.