We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In #79 we started using req2flatpak instead of manually-generated .yaml for wheel-based dependencies.
.yaml
But we left the other deps using the flatpak-pip-generator technique (builds from source).
flatpak-pip-generator
Maybe we should port them all to req2flatpak, by using it to process upstream's requirements.txt.
req2flatpak
requirements.txt
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In #79 we started using req2flatpak instead of manually-generated
.yaml
for wheel-based dependencies.But we left the other deps using the
flatpak-pip-generator
technique (builds from source).Maybe we should port them all to
req2flatpak
, by using it to process upstream'srequirements.txt
.The text was updated successfully, but these errors were encountered: