Red Hat Bugzilla – Bug 614533
[RFE] What about shipping rarpd
Last modified: 2014-11-09 17:33:23 EST
I just did a merge review of rarpd (bug #226355)
and found out that there's no more upstream for rarpd as a separate program
and that rarpd is now part of iputils.
Looking into latest source of iputils,
I see there's rarpd source code and man page.
iputils RELNOTES say:
* rarpd is moved from separate package here (people asked)
So why not shipping rarpd with iputils (which has living upstream)
and let the rarpd (the separate package) be obsoleted by iputils ?
There are no changes in rarpd for long time and first of all this movement would be confusing for users. Another effect is necessity to update iputils when rarpd update will be available and vice versa.
Therefore I prefer to let it be and I'm going to close it 'notabug'.
(In reply to comment #1)
> There are no changes in rarpd for long time and first of all this movement
> would be confusing for users.
When you add
Obsoletes: rarpd < ss981107-31
into iputils.spec then the only visible change for the user would be,
that yum offers him to install iputils when typing 'yum install rarpd'.
> Another effect is necessity to update iputils
> when rarpd update will be available and vice versa.
I don't understand this argument. When the iputils upstream changes something in rarpd code and releases new version of iputils, you will update iputils anyway, don't you ?
> Therefore I prefer to let it be and I'm going to close it 'notabug'.
But it's your decision. So, I let this be too.