[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220802013018.5897f161.tomasz.warniello@gmail.com>
Date: Tue, 2 Aug 2022 01:30:18 +0200
From: Tomasz Warniełło <tomasz.warniello@...il.com>
To: Mauro Carvalho Chehab <mchehab@...nel.org>
Cc: Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
ksummit-discuss@...ts.linuxfoundation.org,
Akira Yokosawa <akiyks@...il.com>
Subject: Re: [PATCH v2 0/5] Address some issues with sphinx detection
On Sat, 2 Jul 2022 11:11:24 +0100
Mauro Carvalho Chehab <mchehab@...nel.org> wrote:
> There are two options to install Sphinx:
>
> - via distro-provided packages;
> - via pip, using virtualenv/venv.
There are countless ways to install any software. So much for my entrée.
*
I don't know this script. Just what I've read in this thread and what I could
extract from it in no more than ten minutes. I understand what it does - or
rather I do just approximately. And alright! Why not help the Gentoos and
Fedoras and Etc's. Noble.
But - wouldn't it be million times easier for all parties to base the support
on a Dockerfile? Or a script producing the right Dockerfile possibly,
considering matters like Java Script opt- ins and outs. If this is not a
cheap pedantry in this context. I don't know.
These here bases look quite official:
https://hub.docker.com/u/sphinxdoc
(Not that I've used them or know them.)
The admins of whichever distribution will find their ways in the mesh, raw
requirements suffice.
The non-admins may have problems with installing software and also running
Docker, as that provides su powers in the straight scenario. `pip` comes as
an alternative, if I'm not wrong. So maybe this pair is the golden arrow?
--thanks
T
Powered by blists - more mailing lists