All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Walters <walters@verbum.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@yoctoproject.org
Subject: Re: non-upstreamed patches
Date: Tue, 03 Jan 2012 13:45:04 -0500	[thread overview]
Message-ID: <1325616304.23339.8.camel@lenny> (raw)
In-Reply-To: <1321315533.1741.26.camel@lenny>

>> On Mon, 2011-11-14 at 22:44 +0000, Richard Purdie wrote:

> > Our current hack is really the former approach - add dummy copies in.
> > Its just a little incomplete and we should enhance it deal with that so
> > we can run gtkdocize.

Revisiting this thread - so I've now created in GNOME git a tiny new
module "gtk-doc-stub" which contains enough bits to build modules from
git with --disable-gtk-doc.

http://git.gnome.org/browse/gtk-doc-stub

It should be enough to add this to Yocto, and then hacking up GNOME
modules to remove GTK_DOC_CHECK from configure.ac etc. should be
unnecessary.  I'm using it now in my self-hosting OS build tool to avoid
wading into Docbook dependency hell.





      parent reply	other threads:[~2012-01-03 18:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13  0:57 non-upstreamed patches Colin Walters
2011-11-13  9:28 ` Koen Kooi
2011-11-13 17:16   ` Colin Walters
2011-11-13 19:51     ` Koen Kooi
2011-11-13  9:47 ` Richard Purdie
2011-11-14 19:06   ` Colin Walters
2011-11-14 19:56     ` Richard Purdie
2011-11-14 20:48       ` Colin Walters
2011-11-14 22:44         ` Richard Purdie
2011-11-15  0:05           ` Colin Walters
2011-11-15  0:19             ` Richard Purdie
2012-01-03 18:45             ` Colin Walters [this message]

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=1325616304.23339.8.camel@lenny \
    --to=walters@verbum.org \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.