From: Akira Yokosawa <akiyks@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: hch@lst.de, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH 1/1] scripts: sphinx-pre-install: add required ctex dependency
Date: Thu, 6 Jan 2022 07:57:22 +0900 [thread overview]
Message-ID: <84f90b41-7a18-d83c-8739-1d394175f74a@gmail.com> (raw)
In-Reply-To: <20220105224230.0700351f@coco.lan>
On Wed, 5 Jan 2022 22:42:30 +0100, Mauro Carvalho Chehab wrote:
> Em Wed, 5 Jan 2022 21:09:59 +0900
> Akira Yokosawa <akiyks@gmail.com> escreveu:
>
[...]
>>
>> I'll test it under various distros/setups.
>> It may take a while.
>
> Did a quick test here with this lxc container:
>
> $ OS=debian REL=bullseye ;lxc-create -n ${OS} -t /usr/share/lxc/templates/lxc-download -- --dist ${OS} --release ${REL} --arch amd64
>
> If we add check_missing_tex(), it will then complain about lots
> of packages that don't exist in Debian (se logs at the end).
Now I think I understand what kind of tests we need.
My plan was to intentionally uninstall texlive-ctex (or whichever
package contains ctexhook.sty) and see if the lack of ctexhook.sty
is detected or not.
Apparently, such a test would mean little for sphinx_pre_install.
>
> That's one of the biggest issue with texlive: each distro splits it on
> different ways. So, basically, the %texlive hash at the script is meant
> to the way Fedora and openSuse distros usually map packages. I would
> expect that Mageia would also be similar if not identical, but other
> distros map packages on different ways.
>
> I'll prepare another patch for fixing the debian issue.
Then I'll wait for it.
Thanks, Akira
>
> Regards,
> Mauro
>
> ---
>
> mchehab@debian:~/docs$ make pdfdocs
> Documentation/Makefile:41: The 'sphinx-build' command was not found. Make sure you have Sphinx installed and in PATH, or set the SPHINXBUILD make variable to point to the full path of the 'sphinx-build' executable.
>
> Detected OS: Debian GNU/Linux 11.
> Warning: better to also install "convert".
> Warning: better to also install "dot".
> Warning: better to also install "dvipng".
> Warning: better to also install "fonts-dejavu".
> Warning: better to also install "fonts-noto-cjk".
> ERROR: please install "gcc", otherwise, build won't work.
> Warning: better to also install "latexmk".
> ERROR: please install "python", otherwise, build won't work.
> Warning: better to also install "rsvg-convert".
> Warning: better to also install "texlive-amscls".
> Warning: better to also install "texlive-amsfonts".
> Warning: better to also install "texlive-amsmath".
> Warning: better to also install "texlive-anyfontsize".
> Warning: better to also install "texlive-capt-of".
> Warning: better to also install "texlive-cmap".
> Warning: better to also install "texlive-ctex".
[...]
next prev parent reply other threads:[~2022-01-05 22:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:30 make pdfdocs fails on Debian stable Christoph Hellwig
2022-01-03 16:58 ` Mauro Carvalho Chehab
2022-01-03 17:11 ` Christoph Hellwig
2022-01-03 20:58 ` Mauro Carvalho Chehab
2022-01-03 21:01 ` [PATCH 0/1] Detect the need of texlive-ctex Mauro Carvalho Chehab
2022-01-03 21:01 ` [PATCH 1/1] scripts: sphinx-pre-install: add required ctex dependency Mauro Carvalho Chehab
2022-01-03 22:46 ` Jonathan Corbet
2022-01-04 0:04 ` Akira Yokosawa
2022-01-04 1:54 ` Akira Yokosawa
2022-01-04 8:05 ` Mauro Carvalho Chehab
2022-01-04 10:26 ` Akira Yokosawa
2022-01-05 7:48 ` Mauro Carvalho Chehab
2022-01-05 12:09 ` Akira Yokosawa
2022-01-05 21:42 ` Mauro Carvalho Chehab
2022-01-05 22:57 ` Akira Yokosawa [this message]
2022-01-06 0:41 ` [PATCH v2] scripts: sphinx-pre-install: Fix ctex support on Debian Mauro Carvalho Chehab
2022-01-06 2:00 ` Akira Yokosawa
2022-01-06 22:35 ` Jonathan Corbet
2022-01-06 0:42 ` [PATCH 1/1] scripts: sphinx-pre-install: add required ctex dependency Mauro Carvalho Chehab
2022-01-04 2:00 ` Akira Yokosawa
2022-01-04 6:47 ` make pdfdocs fails on Debian stable Christoph Hellwig
2022-01-04 7:32 ` Akira Yokosawa
2022-01-04 7:36 ` Christoph Hellwig
2022-01-04 7:53 ` Akira Yokosawa
2022-01-04 7:56 ` Christoph Hellwig
2022-01-04 8:07 ` Akira Yokosawa
2022-01-04 8:16 ` Christoph Hellwig
2022-01-04 8:44 ` Akira Yokosawa
2022-01-04 9:31 ` Akira Yokosawa
2022-01-04 13:19 ` Christoph Hellwig
2022-01-04 13:46 ` Akira Yokosawa
2022-01-05 1:47 ` Akira Yokosawa
2022-01-05 7:35 ` Christoph Hellwig
2022-01-05 12:03 ` Akira Yokosawa
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=84f90b41-7a18-d83c-8739-1d394175f74a@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.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
all inboxes | Powered by JetHome®