Bug 11992 - should packages depend on xinetd!?
should packages depend on xinetd!?
Status: CLOSED NOTABUG
Product: Red Hat Raw Hide
Classification: Retired
Component: xinetd (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-06-08 14:44 EDT by Michael Tokarev
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-06-08 14:44:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Tokarev 2000-06-08 14:44:19 EDT
This is not really a bug in xinetd itself.
RH seemed to switch from inted to xinetd now,
and made some updates to other packages to include
dependance of xnietd.  I will consider it a bug, since
there is no bad things in just adding file to /etc/xinetd.d,
and not requiring xinetd itself.  Why place additional dependance?
I want to use old-good inetd (that is owned by redhat now,
and should be forget?), but any new package I install requires
to install xinetd from me.  Not good.
Comment 1 Trond Eivind Glomsrxd 2000-06-08 14:48:12 EDT
I am planning of removing those, but inetd will not be included with or
supported with our next release. And if those packages are to be useful, and not
just wasted disk space, xinetd.d is required in the distribution setting.

Note You need to log in before you can comment on or make changes to this bug.