public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: Yishai Hadas
	<yishaih-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Alex Rosenbaum
	<rosenbaumalex-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Majd Dibbiny <majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	alaa-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-core] Support writing man pages in MarkDown
Date: Wed, 27 Dec 2017 10:44:44 -0700	[thread overview]
Message-ID: <20171227174444.GC31310@mellanox.com> (raw)
In-Reply-To: <1514368433.4412.2.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>

On Wed, Dec 27, 2017 at 10:53:53AM +0100, Benjamin Drung wrote:
> > > Am Sonntag, den 24.12.2017, 14:03 +0200 schrieb Yishai Hadas:
> > On 12/13/2017 12:59 AM, Jason Gunthorpe wrote:
> > > > pandoc is fairly widely available in the distros with the notable
> > > problem that centos 6 and 7 can only get it from EPEL.
> > > 
> > 
> > There might be even a worse case scenario where pandoc may not exist
> > as 
> > a package to be installed, for example how about SLES OS ?
> 
> The release tarball could contain pre-built man page. So in case the OS
> does provide pandoc to regenerate the man pages, the pre-built can be
> used.

Yes, this is my basic thinking. If pandoc is installed then the
pre-built can be ignored, otherwise they are used so the build can
succeed.

I was thinking of a scheme like
 buildlib/man-cache/<sha1 of .md file>

So if the .md files are changed for any reason then the build will
fail.

> Please do not place generated files in the git repository. 

Realistically, I don't know if this is possible... Too many developers
are using quite old distros these days, and they still have to be
able to build..

I guess we just turn off man page generation in ./build.sh ?

But, how will 'cubild pkg centos6' work?

The release .tar.gz files are created by travis
(buildilb/github-release) so it would not be too hard to
have it also build the cache.

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:[~2017-12-27 17:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 22:59 [PATCH rdma-core] Support writing man pages in MarkDown Jason Gunthorpe
     [not found] ` <20171212225936.GA29558-uk2M96/98Pc@public.gmane.org>
2017-12-12 23:11   ` Hefty, Sean
     [not found]     ` <1828884A29C6694DAF28B7E6B8A82373AB1C234C-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2017-12-12 23:27       ` Jason Gunthorpe
2017-12-24 12:03   ` Yishai Hadas
     [not found]     ` <455f0faf-516b-fa8d-c0d2-d2cee9194e5b-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2017-12-27  9:53       ` Benjamin Drung
     [not found]         ` <1514368433.4412.2.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-12-27 11:13           ` Leon Romanovsky
     [not found]             ` <20171227111348.GB3494-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-12-27 11:27               ` Benjamin Drung
     [not found]                 ` <1514374021.4412.9.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-12-27 12:20                   ` Leon Romanovsky
     [not found]                     ` <20171227122056.GD3494-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-12-27 13:56                       ` Benjamin Drung
2017-12-27 17:44           ` Jason Gunthorpe [this message]
     [not found]             ` <20171227174444.GC31310-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-12-27 18:06               ` Benjamin Drung

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=20171227174444.GC31310@mellanox.com \
    --to=jgg-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=alaa-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=rosenbaumalex-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=yishaih-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@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