From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: quentin.schulz@cherry.de, docs <docs@lists.yoctoproject.org>,
Michael Halstead <mhalstead@linuxfoundation.org>,
"antonin.godard" <antonin.godard@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [docs] Docs build/workers need inkscape?
Date: Mon, 14 Oct 2024 11:47:17 +0100 [thread overview]
Message-ID: <1d9c6e2c2cb42a4127e0eb1c1eefee9adc5de8f0.camel@linuxfoundation.org> (raw)
In-Reply-To: <6c969fd6-d6b9-41ce-9ed7-a5138414780c@cherry.de>
On Mon, 2024-10-14 at 12:43 +0200, Quentin Schulz via
lists.yoctoproject.org wrote:
> Hi Richard,
>
> On 10/12/24 11:19 AM, Richard Purdie via lists.yoctoproject.org
> wrote:
> > Hi All,
> >
> > We've seeing docs build failures:
> >
> > https://valkyrie.yoctoproject.org//#/builders/34/builds/6
> >
> > The issue is that inkscape isn't installed on the workers and isn't
> > in
> > the docs buildtools tarball either.
> >
> > I'm reluctant to start requiring installing inkscape on all
> > autobuilder
> > workers as we try and keep the packages installed minimal for the
> > other
> > builds.
> >
> > I'm wondering if we should just pre-generate those png files
> > alongside
> > the svg sources? I can send a patch doing that...
> >
>
> This will necessarily mean we'll forget to update one or the other :/
> It's bound to happen.
Well, one is clearly derived from the other and listed in the makefile
so I'd hope that makes it clear and relatively easy to fix.
I know what you mean though.
> librsvg is Rust-based IIRC, so that adds up A LOT of build time to
> generate the buildtools tarball.
I think that ship has sailed...
> For my company's user manual, we use rsvg-convert (which seems to be
> coming from librsvg :) ).
That could be easier for us to build rather than the whole of inkscape.
Cheers,
Richard
next prev parent reply other threads:[~2024-10-14 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 9:19 Docs build/workers need inkscape? Richard Purdie
2024-10-12 9:28 ` Alexandre Belloni
2024-10-14 10:43 ` [docs] " Quentin Schulz
2024-10-14 10:47 ` Richard Purdie [this message]
2024-10-14 13:28 ` Antonin Godard
2024-10-14 13:45 ` Alexander Kanavin
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=1d9c6e2c2cb42a4127e0eb1c1eefee9adc5de8f0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=mhalstead@linuxfoundation.org \
--cc=quentin.schulz@cherry.de \
/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