Hyperbola is NOT Arch GNU/Linux. It shares basics, sure. But this does not mean we can import and will adapt those packages. And also: If we would adapt this kind of package we would open an invitation for further problems. There is a reasoning to do packaging absolutely manual. Not only that we need then the blacklisting: Why should we include something with needed blacklisting? People should care what is installed on their systems, not to give away responsibility for someone looking everytime with a concrete listing as this needs even more time to get renewed with more entries. The time the blacklist was done is surely a bit behind, so we also would need to add uncountable numbers of names and packages from everywhere (not only Arch GNU/Linux). Linux (without GNU) is an area to leave for reasoning, with just growing non-free parts and so many problems only with foul compromises. And just because a package does not have direct dependencies for problems does not mean those won't later occur. Automatic created package-buildscripts can result within a complete desaster! Using software-frameworks is complicated as they simulate something you will surely never have with them: Control. Generating automated scripts is the same result: You better understand what components are in use and especially why as the resulting package is therefore also better to debug when errors are there.

I close this thread for the moment: If there is interest to help - and help is surely welcome at any time on any way - you all know the places to get information. If you want to look out for hyperinstaller: https://git.hyperbola.info:50100/~team/ … aller.git/
Again also: Sorry, but development and testing is needed, packaging not. So helpers are surely nice, thanks to acknowledge them here. But we have no problem with python-packages, we have missing man-power for python-development.

https://aur.archlinux.org/packages/pip2arch-git

This doesn''t require pip to use and possibly someone could presumably make it so that, if any software you install with it is on the current blacklist, it  will fail.

Btw, as a huge aside, I forgot to send you something till now, which I placed in this upload area:

https://upload.disroot.org/r/s1YSvx2j#/ … 8lDEUjvsQ=

Thanks, but: The problem is here that pip is needed and we don't include it or will be packaging it. We have hyperman (pacman), there is no need for another package-management outside even breaking possible free and libre parts with adding non-free licensed packages outside the HOME-folder of users.

Ah yeah, I see it'd have to be done from a different machine or a spare with pip. If that's even worth the effort.

https://aur.archlinux.org/packages/pipman-git
https://aur.archlinux.org/packages/pip2arch-git
https://aur.archlinux.org/packages/python-pypi2pkgbuild

we need support with the further development of some of our Python- and Perl-based packages. To name them here as follows:

hyperinstaller: This application needs further testing and fixing problems. You can review the code here
hypervideo: We need here people looking after the development and support heckyel. You can look onto the package here
fair-viewer: We need here people looking after the development and support heckyel. You can look onto the package here
yt-local: We need here people looking after the development and support heckyel. You can look onto the package here

The package yt-local would be for sure not the highest priority. For the others besides hyperinstaller we need first also to import the needed data into our local repositories. If you have further interest to help us with the development and be for sure part of the team: Just leave a message here or contact us within IRC or mail. Thanks!