On Mon, Nov 9, 2020 at 9:32 PM Todd Zullinger <t...@pobox.com> wrote:
> Hi, > > Sérgio Basto wrote: > > Like tftp we may replace xinetd by systemd service files [1] , > > if we replace cvs-inetd by a systemd service, the problem is solved. > > > > [1] > > > https://src.fedoraproject.org/rpms/tftp/c/15a26fcde8a0078766b6bbba183d89f920e51535?branch=master > > The cvs package has supported systemd for years. There is > simply an inetd subpackage which provides support for xinetd > still. > > If xinetd is left orpahaned and retired, dropping the inetd > subpackage from cvs might look something like: > > https://src.fedoraproject.org/fork/tmz/rpms/cvs/c/ee901571db > > I didn't file that as PR yet because it's not clear whether > xinetd will be adopted or not. > > But it should be relatively easy for us (in the sense of > most any interested packager) to remove the xinetd dep from > cvs. > > -- > Todd > > Why not split the cvs package like git and create a cvs-core package that actually contains the cvs executables/files and then only BR/require that from git/git-cvs? That would be the more immediate solution that prunes the affected packages from the xinetd orphaning by quite a lot. -Ian
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
