lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAFttn56VFPjikxjhgds6LjphinStm_cN+7ZhAzsieT0gnBqBDQ@mail.gmail.com>
Date: Thu, 5 Jun 2025 17:29:13 +0530
From: Sai Vishnu <saivishnu725@...il.com>
To: mchehab@...nel.org
Cc: corbet@....net, linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, 
	skhan@...uxfoundation.org
Subject: [RFC PATCH 00/04] scripts: sphinx-pre-install: add interactive option

This RFC proposes adding an interactive mode to the sphinx-pre-install script
to guide users through installing missing dependencies for setting up sphinx.
The goal is to enhance usability by prompting users to execute distro-specific
commands, improving the experience for developers setting up the documentation
builds.

Based on feedback from the initial RFC, this series restarts fresh to outline
the planned approach. The feature will take 4 patches to completely implement,
each addressing a different section of the feature.

Planned patch series:
1. Add --interactive flag and update the script's "Usage" message
2. Implement the run_if_interactive and other helper functions
3. Add a fallback to distro detection and verify the user's choice
    - Why? A user running Pop!_OS can utilize hints based on Ubuntu
     but the script will not detect and return a "Unknown distro" message
    - Add a package manager check for each distro-specific function to
     verify the user's choice. Avoids running harmful/unsupported commands
4. Apply interactive mode to distro-specific hints - Integration

Please provide feedback/advice if necessary. Patches are ready and will be sent
in 2-3 days after gathering any possible feedback.

Please provide feedback, especially on:
1. Whether to merge patches 1 and 2
    - They are both setting the starting point for the entire feature
2. How to deal with commands in recommend_sphinx_version()
    - Two possible routes exist to install sphinx
    - Available options: pip/pypi or distro-specific package manager
    - The plan is to add a prompt that asks the user to specify a number
     1 for pip, 2 for package manager, 0 to skip

Initial RFC
RFC: https://lore.kernel.org/all/20250410155414.47114-1-saivishnu725@gmail.com/
Feedback: https://lore.kernel.org/all/87ikn6bw34.fsf@trenco.lwn.net

Thank you for the time and response!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ