CONTRIBUTING: Clearify packaging policy on python packages
We have the possibility to cross-compile python modules thanks to @xtkoba's work on termux_setup_python_crossenv [1], but IMO only core python packages, or packages that cannot be installed through pip should be added as termux packages. [1] https://github.com/termux/termux-packages/blob/master/scripts/build/setup/termux_setup_python_crossenv.sh
This commit is contained in:
parent
6af783bca9
commit
343f786e97
|
@ -100,10 +100,10 @@ met these conditions:
|
|||
|
||||
- **Not installable through cpan, gem, npm, or pip**
|
||||
|
||||
These packages should be installable through `cpan`, `gem`, `npm`, `pip` and
|
||||
These packages should be installed through `cpan`, `gem`, `npm`, `pip` and
|
||||
so on.
|
||||
|
||||
Packaging modules for Perl, Ruby, Node.js, Python is problematic, especially
|
||||
Packaging modules for Perl, Ruby, Node.js, is problematic, especially
|
||||
when it comes to cross-compiling native extensions.
|
||||
|
||||
- **Not taking too much disk space**
|
||||
|
|
Loading…
Reference in New Issue