sabnzbd: python target dependencies

[tqfx]

Close #20060

[tqfx]

How about using termux_step_post_get_source to get the main dependencies of this python target?

termux_step_post_get_source() {
	export TERMUX_PKG_PYTHON_TARGET_DEPS=""
	while IFS="" read -r dep
	do
		if [ -z "$dep" ]; then
			break
		fi
		dep="${dep/[# ]*}"
		if [ -z "$dep" ]; then
			continue
		fi
		TERMUX_PKG_PYTHON_TARGET_DEPS+="'$dep', "
	done < $TERMUX_PKG_SRCDIR/requirements.txt
}

Don't want to worry about tomorrow!

[licy183]

For this package, parsing them from requirements.txt seems okay, because it is not a regular python package, but a program using python.

Maybe it is off-topic, but I want to discuss this issue for other regular python packages.

In fact, in python packages, requirements.txt does not guarantee that all existing items are runtime dependencies - it may contain some build-time dependencies, or some dependencies that exist when building the extra module. If possible, a better approach is to get the METADATA file from the already-built wheel and read the Requires-Dist entry from it. Besides, just installing the package itself in postinst will be a possible approach to this issue too.

termux_step_create_debscripts() {
	cat <<- EOF > ./postinst
	#!$TERMUX_PREFIX/bin/sh
	echo "Installing dependencies through pip..."
	pip3 install the-package-name
	EOF
}

[TomJo2000]

I think we're good to merge this in the meantime.

[licy183]

Thanks!