Hello, I want to submit five packages to the AUR for the Psono Password Manager. It's open source and I got permission from the developer to do so with the disclaimer that they are not officially supported. Three of these packages require a python virtual environment (due to the extensive list of python dependencies that are not available in the Arch Linux repositories) and the way I initially approached this was to use the post_install() function in the install script. Here's the PKGBUILD review link on the forums: https://bbs.archlinux.org/viewtopic.php?id=312591 With the advice of Lone_Wolf and twelveeighty I moved the venv creation to the build() function of the PKGBUILD. Psono is only available in a docker image format so I created a custom dlagent to download the docker image, extract the software I need for the package, tarball it and use the tarball as a source file for hash verification. Using a constant mtime value while creating the tarball makes sure the hash stays the same with the same files if they aren't changed upstream. My question for the AUR moderators and package maintainers is as follows: the python venv is created when building the package and is shipped with the package. Is this acceptable for the AUR? What's your opinion? Am I allowed to submit these packages like they are? I also attached one of the three packages' source so you can test building it yourself. Currently it doesn't have licenses set up yet. It's the enterprise edition of Psono's server software. There's also a community edition available that's free that I also intend to submit if allowed. The hashes should be up to date with the enterprise edition. Let me know what you think. Kind regards, 7thCore