kamp/fdroidserver
1
0
Fork 0
mirror of https://gitlab.com/fdroid/fdroidserver.git synced 2024-11-04 22:40:12 +01:00
Code Activity
7ef0d5dfd8
fdroidserver/setup.py

51 lines
1.5 KiB
Python
Raw Normal View History

Switch all headers to python3
2016-01-04 16:33:20 +01:00
#!/usr/bin/env python3
Make the server tools an installable package (with distutils) - wip
2012-03-11 12:59:19 +01:00
convert setup.py into working setuptools-based installer With this setup.py, its possible to install the required packages using: pip install -e . The Debian packaging will also automatically get the dependencies from install_requires. This does not handle the generation of the docs at all. I have not found a straightforward way to include running ./gendocs.sh in setup.py, but its easy to run in the Debian packaging.
2013-10-24 21:29:40 +02:00
from setuptools import setup
Fix installs with pip --user
2017-04-03 14:55:20 +02:00
import os
include prefix in data_files install path so it installs correctly setuptools wants to stick any relative install path in data_files into the .egg package. Things are not setup to use the egg now. We might want to consider using sticking files into the egg via pkg_resource in the future.
2014-04-02 20:41:20 +02:00
import sys
Make the server tools an installable package (with distutils) - wip
2012-03-11 12:59:19 +01:00
Fix installs with pip --user
2017-04-03 14:55:20 +02:00
# workaround issue on OSX or --user installs, where sys.prefix is not an installable location
if os.access(sys.prefix, os.W_OK | os.X_OK):
fix installing via OSX's easy_install
2015-07-31 14:47:48 +02:00
data_prefix = sys.prefix
Fix installs with pip --user
2017-04-03 14:55:20 +02:00
else:
data_prefix = '.'
fix installing via OSX's easy_install
2015-07-31 14:47:48 +02:00
downcase setup.py name to match the name in the repo, Debian package, etc.
2014-04-02 20:38:57 +02:00
setup(name='fdroidserver',
Bump to 0.7.0
2016-09-11 11:52:11 +02:00
version='0.7.0',
Make the server tools an installable package (with distutils) - wip
2012-03-11 12:59:19 +01:00
description='F-Droid Server Tools',
Correct filename in setup.py
2015-08-04 21:02:06 +02:00
long_description=open('README.md').read(),
Make the server tools an installable package (with distutils) - wip
2012-03-11 12:59:19 +01:00
author='The F-Droid Project',
Fix email, url and docs in setup.py
2014-01-08 18:17:00 +01:00
author_email='team@f-droid.org',
url='https://f-droid.org',
Add asynchronous filereader, fix python3 lockups
2015-09-20 20:50:02 +02:00
packages=['fdroidserver', 'fdroidserver.asynchronousfilereader'],
Add fd-commit as script on setup.py
2014-01-15 23:02:02 +01:00
scripts=['fdroid', 'fd-commit'],
install sample config files in a standard location This means they'll automatically be installed in the right place by the packaging processes of various UNIX distros, and then that makes it easy for the upcoming 'fdroid init' to find them.
2013-11-01 20:09:16 +01:00
data_files=[
fix installing via OSX's easy_install
2015-07-31 14:47:48 +02:00
(data_prefix + '/share/doc/fdroidserver/examples',
Add setup.py to pep8+pyflakes hook, fix it
2014-08-16 11:51:23 +02:00
['buildserver/config.buildserver.py',
'examples/config.py',
name makebuildserver config the same as the script This keeps the numbers of names down to a minimum, and since the config is placed right next to the script, this keeps tab completion working nicely when the config file is in place. The old file name is still supported.
2016-01-20 20:38:18 +01:00
'examples/makebuildserver.config.py',
Add setup.py to pep8+pyflakes hook, fix it
2014-08-16 11:51:23 +02:00
'examples/opensc-fdroid.cfg',
'examples/fdroid-icon.png']),
Apply some autopep8-python2 suggestions
2014-12-31 16:42:26 +01:00
],
Rewrite scanner logic Initially, the scanner used libmagic which used magic numbers in the file's content to detect what kind of file it appears to be. Since that library isn't available on all systems, we added support for two other libraries, mimetypes amongst them. The issue with mimetypes is that it only uses the file's extension, not its actual content. So this ends in variable behaviour depending on what system you're using fdroidserver on. For example, an executable binary without extension would be ignored if mimetypes was being used. We now drop all libraries - mimetypes too as it depends on the system's mime.types file - and instead check extensions ourselves. On top of that, do a simple binary content check to find binary executables that don't have an extension. The new in-house code without any dependencies doesn't add any new checks, so no builds should break. The current checks still work: % fdroid scanner app.openconnect:1029 [...] Found executable binary at assets/raw/armeabi/curl Found executable binary at assets/raw/mips/curl Found executable binary at assets/raw/x86/curl Found JAR file at lib/XposedBridgeApi-54.jar Found JAR file at libs/acra-4.5.0.jar Found JAR file at libs/openconnect-wrapper.jar Found JAR file at libs/stoken-wrapper.jar Found shared library at libs/armeabi/libopenconnect.so Found shared library at libs/armeabi/libstoken.so Found shared library at libs/mips/libopenconnect.so Found shared library at libs/mips/libstoken.so Found shared library at libs/x86/libopenconnect.so Found shared library at libs/x86/libstoken.so
2015-09-14 07:11:53 +02:00
install_requires=[
makebuildserver: use original names for downloaded SDK components It will make it a lot easier to manage the cache if we use the original file names, which often include the file version. This also changes the download process to be resumable if there is a partial file in the cache, and switches from calling wget on the command line to using the python libs 'requests' and 'clint' to provide a similar experience. While its not so important for this particular bit of code to use those libraries, I think those two will allow us to provide a better user experience throughout the whole of fdroidserver. In this case, it is already doing special tricks fetching the file size from the server before trying to download it. I suppose this code could instead check if the file exists, and if so, check the hash sum. I think that would be slower for most people since checking the hash on large files takes a noticeable about of time, while a HTTP HEAD request is pretty tiny.
2016-06-10 11:42:42 +02:00
'clint',
import app into fdroid directly from git clone This adds a new method for `fdroid import` that will generate the fdroidserver metadata based on a local git repo. This new mode generates the metadata in the new .fdroid.yaml format in the git repo itself. It is intended as a quick way to get starting building apps using the fdroidserver tools.
2016-03-21 21:00:12 +01:00
'GitPython',
Add setup.py to pep8+pyflakes hook, fix it
2014-08-16 11:51:23 +02:00
'mwclient',
'paramiko',
'Pillow',
'apache-libcloud >= 0.14.1',
Replace getsig.java with a pure python implementation Special thanks to deki for helping out with the certificate encodings: https://gitlab.com/snippets/1842 fixes #5 https://gitlab.com/fdroid/fdroidserver/issues/5
2014-08-30 04:53:55 +02:00
'pyasn1',
'pyasn1-modules',
support app metadata in YAML format YAML is a format that is quite similar to the .txt format, but is a widespread standard that has editing modes in popular editors. It is also easily parsable in python. The .pickle for testing is a lightly edited version of the real metadata for org.videolan.vlc: * comments were removed
2015-07-24 09:42:47 +02:00
'PyYAML',
dscanner - Drozer based post-build dynamic vulnerability scanner command * New command `dscanner`, enables one to scan signed APKs with Drozer * Drozer is a dynamic vulnerability scanner for Android * Drozer runs in a emulator or on-device, this new `dscanner` command... * starts a docker image with Drozer and the Android Emulator pre-installed, * loads the signed APK into the emulator * activates Drozer automated tests for the APK * gathers the report output and places it next to the original APK * The Drozer docker image can be: * cached locally for re-use (just don't run --clean*) * retrieved from dockerhub.com for more efficient runtime * or be built from scratch (in the new "./docker" directory) * New "Vulnerability Scanning" documentation section (run gendocs.sh)
2016-12-06 13:57:04 +01:00
'requests < 2.11',
'docker-py == 1.9.0',
Apply some autopep8-python2 suggestions
2014-12-31 16:42:26 +01:00
],
convert setup.py into working setuptools-based installer With this setup.py, its possible to install the required packages using: pip install -e . The Debian packaging will also automatically get the dependencies from install_requires. This does not handle the generation of the docs at all. I have not found a straightforward way to include running ./gendocs.sh in setup.py, but its easy to run in the Debian packaging.
2013-10-24 21:29:40 +02:00
classifiers=[
Add setup.py to pep8+pyflakes hook, fix it
2014-08-16 11:51:23 +02:00
'Development Status :: 3 - Alpha',
'Intended Audience :: Developers',
setup.py: fix missing comma in classifiers
2016-02-18 11:47:02 +01:00
'License :: OSI Approved :: GNU Affero General Public License v3 or later (AGPLv3+)',
Add setup.py to pep8+pyflakes hook, fix it
2014-08-16 11:51:23 +02:00
'Operating System :: POSIX',
'Topic :: Utilities',
Apply some autopep8-python2 suggestions
2014-12-31 16:42:26 +01:00
],
convert setup.py into working setuptools-based installer With this setup.py, its possible to install the required packages using: pip install -e . The Debian packaging will also automatically get the dependencies from install_requires. This does not handle the generation of the docs at all. I have not found a straightforward way to include running ./gendocs.sh in setup.py, but its easy to run in the Debian packaging.
2013-10-24 21:29:40 +02:00
)
Copy Permalink