xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: "Roger Pau Monné" <roger.pau@entel.upc.edu>,
	"Ian Campbell" <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.2 TODO List Update
Date: Wed, 25 Jan 2012 14:57:47 +0000	[thread overview]
Message-ID: <CB45C8EB.29986%keir.xen@gmail.com> (raw)
In-Reply-To: <CAPLaKK7RiUysAR_xr6Hc2FBf_btj-XvG+3h4FxgbrBaDmF2zCA@mail.gmail.com>

On 25/01/2012 14:49, "Roger Pau Monné" <roger.pau@entel.upc.edu> wrote:

>>> don't want to install it, but I would like to have the man pages when
>>
>>> building Xen from source.
>
> "make -C docs man-pages" will do what you
>>> want.

Thanks, I've already done this to build them on my system, but I
>>> think
we should provide some easy way for users without latex to build
>>> and
install the man pages.

> I must admit I thought latex was optional and
>>> that "make docs" would
> simply skip those docs if it wasn't installed --
>>> that's what the "if
> which $(TOOL)" construct used in there is (supposed to
>>> be) doing.

If latex is not found, the compilation is aborted:

# make
>>> docs
sh ./docs/check_pkgs && make -C docs install ||
>>> true
=================================================
=====================
>>> ============================
= WARNING: Package 'latex' is required
=
>>> to build Xen 
>>> documentation
=================================================
============
>>> =====================================

I think make docs should just skip
>>> latex if not found.

I'm dubious whether the latex docs are at all useful these days. We could
possibly just remove them entirely.

 -- Keir

  reply	other threads:[~2012-01-25 14:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 13:19 Xen 4.2 TODO List Update Ian Campbell
2012-01-23 16:07 ` Ian Campbell
2012-01-23 18:22 ` Dario Faggioli
2012-01-24 14:31 ` Juergen Gross
2012-01-24 19:28   ` Shriram Rajagopalan
2012-01-25 14:33 ` Roger Pau Monné
2012-01-25 14:41   ` Ian Campbell
2012-01-25 14:49     ` Roger Pau Monné
2012-01-25 14:57       ` Keir Fraser [this message]
2012-01-25 15:41         ` Ian Campbell
2012-01-25 14:59       ` Ian Campbell
2012-01-25 15:03         ` Roger Pau Monné
2012-01-25 15:40           ` Ian Campbell
2012-01-25 15:55             ` Keir Fraser
2012-01-26 14:57               ` Roger Pau Monné
  -- strict thread matches above, loose matches on Subject: below --
2012-01-31 11:51 Ian Campbell
2012-01-17 10:00 Ian Campbell
2012-01-17 10:04 ` Roger Pau Monné
2012-01-17 10:08 ` Olaf Hering
2012-01-17 10:53 ` Olaf Hering
2012-01-17 11:02   ` Ian Campbell

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=CB45C8EB.29986%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=roger.pau@entel.upc.edu \
    --cc=xen-devel@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).