jcgruenhage/void-packages
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
152096 commits 2 branches 0 tags 520 MiB
Commit graph

10 commits

Author SHA1 Message Date
Leah Neukirchen
d3968bef3c build-style/python[3]-module: override _PYTHON_SYSCONFIGDATA_NAME 
Use the sysconfigdata for the appropriate cross arch.
Upstream change: https://bugs.python.org/issue36235
 2019-12-23 17:15:51 +01:00
Leah Neukirchen
915fe2de9f common/environment/setup/python.sh: update to Python 3.8. 2019-12-23 14:11:45 +01:00
Piotr Wójcik
a4e3f89907 build-style/python-module.sh: add do_check 2019-03-21 13:28:56 -03:00
maxice8
3e6ea8d31a build-style/python-module: reset CFLAGS and LDFLAGS in each run 2019-01-31 12:22:30 -02:00
Alessio Sergi
2014e03dac Revert "common/buildstyle/python*: build dir can be used as python identifier" 
This reverts commit a02132b2ae.

Actually, the issue with packages using python-distutils-extra hasn't
been solved. On the contrary, python build style now generates malformed
packages, e.g., gufw:

+-- usr
    +-- lib
    |   +-- python3.5
    |       +-- site-packages
    |           +-- build3_5
    |           |   +-- lib
    |           |       +-- gufw
    |           |           +-- __init__.py
    |           |           +-- gufw
    |           |           +-- gufw.py
    |           +-- gufw
    |           |   +-- __init__.py
    |           |   +-- gufw
    |           |   +-- gufw.py
    |           +-- gufw-17.04.1-py3.5.egg-info

I don't have a clean solution handy right now, but that obviously isn't.
 2017-01-12 12:27:12 +01:00
Enno Boland
a02132b2ae common/buildstyle/python*: build dir can be used as python identifier 
in order to make gufw installation process work, it includes itself
while installing. this raise the need that the build directory needs
to be a valid python identifier too. this commit solves this issue.
 2017-01-05 20:53:47 +01:00
Alessio Sergi
4e6576e7a4 xbps-src: add support for python3 pkgs 
- python_module build style now builds modules for python2/3 by default
- new python2_module and python3_module build styles for building
  python2-only and python3-only packages respectively
- no more python_versions
- no need to define pycompile_version for Python modules anymore
  (still needed for non-Python modules though)
- Python version and paths are now guessed automatically and a set of
  useful variables can now be used in templates
- #!/usr/bin/python2 and #!/usr/bin/python3 are now the default shebangs
- /usr/bin/foo2 and /usr/bin/foo3 are now the default names for bin
  scripts (for use with alternatives)
 2016-10-16 16:59:31 +02:00
Alessio Sergi
ffff9d749d build-style/python-module: rename unversioned scripts, if any 
- No more name conflicts in case of multi-version python packages
- No more manual renaming
- No more manual shebang fixes
- Alternatives support

ok xtraeme@
 2016-04-25 01:29:15 +02:00
Alessio Sergi
398e057844 build_style/python-module: unbreak cross builds 2015-02-21 19:21:21 +01:00
Juan RP
df4c861f97 xbps-src: common/{,environment}/build_style -> common/${,environment}/build-style. 2015-02-21 12:13:07 +01:00
Renamed from common/build_style/python-module.sh (Browse further)