Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Takumi Takahashi <takumiiinn@gmail.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Mauro Condarelli <mc5686@mclink.it>,
	Asaf Kahlon <asafka7@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/python-pygments: support host package
Date: Tue, 6 Aug 2024 22:41:42 +0200	[thread overview]
Message-ID: <20240806224142.24555952@windsurf> (raw)
In-Reply-To: <20231001034247.14022-1-takumiiinn@gmail.com>

Hello Takumi,

On Sun,  1 Oct 2023 12:42:46 +0900
Takumi Takahashi <takumiiinn@gmail.com> wrote:

> The reason this patch is needed is because gtk-doc requires pygments.
> The final goal is to submit a patch for lightdm, but since gtk-doc is
> required to build lightdm, pygments will also be required.
> 
> Signed-off-by: Takumi Takahashi <takumiiinn@gmail.com>
> ---
>  package/python-pygments/python-pygments.mk | 1 +
>  1 file changed, 1 insertion(+)

Thanks for your patch, and sorry for the long delay with which we are
getting back to you. However, this patch, as well as the patching
adding itstool need to go together, in a patch series that also adds
the lightdm package. Indeed we want to see the big picture, and not
have those two "orphan" host packages without the actual package using
them.

That being said, I think the approach should rather to make sure that
lightdm doesn't require gtk-doc. In the context of Buildroot, we are
not interested in building the documentation. Are you sure that lightdm
absolutely requires gtk-doc? I see it's using the GTK_DOC_CHECK m4
macro, so it supports --disable-gtk-doc, and that should do the trick.
If not, it should be fixed to do the trick :)

If you're still interested into this, could you send the full series of
patches including lightdm?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-08-06 20:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-30 19:06 [Buildroot] [PATCH] package/python-pygments: support host package Takumi Takahashi
2023-09-30 19:41 ` Thomas Petazzoni via buildroot
2023-10-01  3:11   ` Takumi Takahashi
2023-10-01  3:42 ` [Buildroot] [PATCH v2] " Takumi Takahashi
2024-08-06 20:41   ` Thomas Petazzoni via buildroot [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=20240806224142.24555952@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=james.hilliard1@gmail.com \
    --cc=mc5686@mclink.it \
    --cc=takumiiinn@gmail.com \
    --cc=thomas.petazzoni@bootlin.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