public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Jarod Wilson <jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core] redhat/spec: further cleanups to depdendencies, descriptions, formatting
Date: Thu, 22 Dec 2016 11:35:36 -0700	[thread overview]
Message-ID: <20161222183536.GB5660@obsidianresearch.com> (raw)
In-Reply-To: <bf346322-4ef4-032d-9ea2-5a63ae7737e5-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Thu, Dec 22, 2016 at 01:17:00PM -0500, Jarod Wilson wrote:

> >>- Add explicit dependencies on kmod, initscripts and systemd, as there
> >>  are container and vm cases where there might not be a kernel
> >>  installed
> >
> >Do we need initscripts?
> 
> Not really sure, the Fedora package reviewer insists we do.

Hm, no idea what for. We don't provide any LSB init scripts any more,
right?

> >> Requires: %{name}%{?_isa} = %{version}-%{release}
> >>+Requires: logrotate
> >
> >I don't think we use logrotate for anything unless the srp rsyslog
> >examples are being used? Maybe it would be better to move the logrotate
> >and rsyslog stuff to doc/examples or something?
> 
> This is another one where the package reviewer seems insistent.

By default "journald -u srp_daemon" does the same job, so I view
these files as obsolete for pre-systemd distros.

I think we should just not include the rsyslog and logrotate config
files at all. Sophisticated users that need that stuff can install
rsyslog and setup their own filtering. I assume that is the FC policy?
That avoids the reviewer comment.

It certainly makes 0 sense to Require logrotate without also requiring
rsyslog because rsyslog is the thing that writes the file being
rotated...

Forcing rsyslog is *really* not desirable, most people don't want/need
that overhead. Forcing logrotate is not desirable because it forces a
useless cron job to run and folks in this world are sensitive to that
jitter..

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-12-22 18:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 18:02 [PATCH rdma-core] redhat/spec: further cleanups to depdendencies, descriptions, formatting Jarod Wilson
     [not found] ` <20161222180220.49558-1-jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-12-22 18:13   ` Jason Gunthorpe
     [not found]     ` <20161222181323.GA5053-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-12-22 18:17       ` Jarod Wilson
     [not found]         ` <bf346322-4ef4-032d-9ea2-5a63ae7737e5-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-12-22 18:35           ` Jason Gunthorpe [this message]
     [not found]             ` <20161222183536.GB5660-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-12-22 18:41               ` Doug Ledford
     [not found]                 ` <f5f043f3-a396-ee44-6f7f-ef3b14daae15-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-12-22 19:00                   ` Jason Gunthorpe
     [not found]                     ` <20161222190057.GC5660-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-12-22 19:14                       ` Doug Ledford
2016-12-22 18:13   ` Jarod Wilson
2016-12-22 18:14   ` [PATCH rdma-core v2] " Jarod Wilson
     [not found]     ` <20161222181404.57469-1-jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-09 21:39       ` [PATCH rdma-core v3] " Jarod Wilson
     [not found]         ` <20170109213910.31871-1-jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-09 22:36           ` Jason Gunthorpe
     [not found]             ` <20170109223631.GB10850-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-10  3:20               ` Jarod Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161222183536.GB5660@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=jarod-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox