kamp/fdroidserver
1
0
Fork 0
mirror of https://gitlab.com/fdroid/fdroidserver.git synced 2024-11-09 17:00:12 +01:00
Code Activity
d31856b6c7
fdroidserver/tests/metadata/dump/org.videolan.vlc.yaml

2649 lines
49 KiB
YAML
Raw Normal View History

update: AllowedAPKSigningKeys metadata to enforce APK signers This field lets you specify which signing certificates should be trusted for APKs in a binary repo.
2021-07-20 22:31:27 +02:00
AllowedAPKSigningKeys: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
AntiFeatures: {}
metadata: Make ArchivePolicy an interger internally
2023-05-25 19:05:57 +02:00
ArchivePolicy: 9
convert App to subclass of dict to support parsing/dumping libs Python is heavily based on its core data types, and dict is one of the more important ones. Even classes are basically a wrapper around a dict. This converts metadata.App to be a subclass of dict so it can behave like a dict when being dumped and loaded. This makes its drastically easier to use different data formats for build metadata and for sending data to the client. This approach will ultimately mean we no longer have to maintain custom parsing and dumping code. This also means then that the YAML/JSON field names will not have spaces in them, and they will match exactly what it used as the dict keys once the data is parsed, as well as matching exactly the instance attribute names: * CurrentVersion: 1.2.6 * app['CurrentVersion'] == '1.2.6' * app.CurrentVersion == '1.2.6' Inspired by: https://goodcode.io/articles/python-dict-object/
2016-11-23 17:25:59 +01:00
AuthorEmail: null
AuthorName: null
support "Author Web Site" as metadata field Fastlane Supply, Triple-T Gradle Play Publisher, and many app stores include the possibility to specify a website for the author, as distinct from the website for the app. closes #204
2017-04-14 14:23:07 +02:00
AuthorWebSite: null
convert App to subclass of dict to support parsing/dumping libs Python is heavily based on its core data types, and dict is one of the more important ones. Even classes are basically a wrapper around a dict. This converts metadata.App to be a subclass of dict so it can behave like a dict when being dumped and loaded. This makes its drastically easier to use different data formats for build metadata and for sending data to the client. This approach will ultimately mean we no longer have to maintain custom parsing and dumping code. This also means then that the YAML/JSON field names will not have spaces in them, and they will match exactly what it used as the dict keys once the data is parsed, as well as matching exactly the instance attribute names: * CurrentVersion: 1.2.6 * app['CurrentVersion'] == '1.2.6' * app.CurrentVersion == '1.2.6' Inspired by: https://goodcode.io/articles/python-dict-object/
2016-11-23 17:25:59 +01:00
AutoName: VLC
AutoUpdateMode: None
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
Binaries: null
Bitcoin: null
eliminate app.builds everywhere, it should be app['Builds'] The .txt format was the last place where the lowercase "builds" was used, this converts references everywhere to be "Builds". This makes it possible to load metadata YAML files with any YAML parser, then have it possible to use fdroidserver methods on that data, like metadata.write_metadata(). The test files in tests/metadata/dump/*.yaml were manually edited by cutting the builds: block and putting it the sort order for Builds: so the contents should be unchanged. ``` sed -i \ -e 's/app\.builds/app.get('Builds', \[\])/g' \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\])/app.get('Builds', \[\])/g" \ -e "s/app\.get('Builds', \[\])\.append/app\['Builds'\].append/g" \ -e "s/app\['builds'\]/app.get('Builds', [])/g" \ */*.* ```
2020-12-09 16:01:21 +01:00
Builds:
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate:
- .
- ../java-libs/SlidingMenu
- ../java-libs/ActionBarSherlock
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.0.11
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: true
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '48d' ../Makefile
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs: []
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 110
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.0.11-ARMv7
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate:
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
- .
- ../java-libs/SlidingMenu
- ../java-libs/ActionBarSherlock
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.0.11
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: true
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '48d' ../Makefile
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs: []
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 111
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.0.11-ARM
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate:
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
- .
- ../java-libs/SlidingMenu
- ../java-libs/ActionBarSherlock
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: unknown - see disabled
disable: ffmpeg error 0.0.11
encoding: null
extlibs: []
forcevercode: true
forceversion: true
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '48d' ../Makefile
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs: []
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 112
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.0.11-x86
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate:
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
- .
- ../java-libs/SlidingMenu
- ../java-libs/ActionBarSherlock
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=mips ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.0.11
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: true
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '48d' ../Makefile
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs: []
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 113
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.0.11-mips
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=mips ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.1.3
disable: build failing (at 0.1.3)
encoding: null
extlibs: []
forcevercode: true
forceversion: true
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch:
- ndkr9.patch
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7c52aacbe
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1301
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.1.3-MIPS
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.1.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: true
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch:
- ndkr9.patch
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7c52aacbe
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1302
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.1.3-x86
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.1.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: true
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch:
- ndkr9.patch
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7c52aacbe
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1303
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.1.3-ARM
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.1.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: true
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch:
- ndkr9.patch
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7c52aacbe
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1304
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.1.3-ARMv7
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.0
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@31ffb20309264994
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9002
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.0
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.0
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@31ffb20309264994
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9004
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.0
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@37e886d113b8b567c15208579fb2f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9102
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@37e886d113b8b567c15208579fb2f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9104
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.5
disable: can't download gmp
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@052600173f376ff58ff04d53746961a2
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9502
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.5
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.5
disable: can't download gmp
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@052600173f376ff58ff04d53746961a2
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9504
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.5
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.6
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@27f4799
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9602
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.6
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.6
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@27f4799
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9604
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.6
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.7
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@9e1c6ff
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9702
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.7
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.7
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@9e1c6ff
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9704
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.7
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=mips ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.7.1
disable: build fails
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@57cd36b
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9711
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.7.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.7.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@57cd36b
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9712
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.7.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.7.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@57cd36b
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9714
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.7.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.8
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@f2db364
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9802
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.8
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.8
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@f2db364
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9803
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.8
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.8
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@f2db364
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9804
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.8
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.9
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@e731dc23a4f8ef6782c7cc2236bbbf41c034dad1
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9902
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.9
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.9
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@e731dc23a4f8ef6782c7cc2236bbbf41c034dad1
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9903
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.9
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.9
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@e731dc23a4f8ef6782c7cc2236bbbf41c034dad1
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9904
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.9
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.10
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@e33e5de
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10002
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.10
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.10
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@e33e5de
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10003
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.10
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 0.9.10
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@e33e5de
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10004
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.9.10
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.0.0
disable: doesn't build
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@036010e
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10006
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.0.0
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.0.0
disable: doesn't build
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@036010e
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10007
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.0.0
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.0.0
disable: doesn't build
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@036010e
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10008
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.0.0
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=x86 ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.0.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@59409d5
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10102
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.0.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.0.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@59409d5
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10103
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.0.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ANDROID_ABI=armeabi-v7a ./compile.sh release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.0.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i '/ant/d' ../Makefile && ln -s vlc-android/$$VLC-2.2$$ ../vlc
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC-2.2@59409d5
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 10104
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.0.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@a9b19e4
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010303
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@a9b19e4
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010304
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@a9b19e4
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010305
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.5
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@e6b4585
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010503
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.5
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.5
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@e6b4585
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010504
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.5
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.5
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@e6b4585
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010505
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.5
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.6
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@551b670
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010603
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.6
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.6
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@551b670
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010604
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.6
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.1.6
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@551b670
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1010605
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.1.6
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.0
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@23c8d86
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020003
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.0
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.0
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@23c8d86
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020004
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.0
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.0
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@23c8d86
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020005
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.0
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@23c8d86
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020103
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@23c8d86
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020104
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@23c8d86
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020105
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.2
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020203
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.2
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.2
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020204
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.2
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.2
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020205
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.2
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020303
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020304
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020305
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.4
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020403
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.4
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.4
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020404
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.4
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.4
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@7491a5f
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020405
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.4
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.5
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@50accb8
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020503
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.5
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.5
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@50accb8
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020504
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.5
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.5
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@50accb8
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1020505
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.5
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.6
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv6fpu
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@d59b81a
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1030003
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.6
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "armeabi-v7a" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.6
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaARMv7
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@d59b81a
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1030004
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.6
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
build:
- cd ../ && ./compile.sh -a "x86" --release
normalize Build TYPE_LIST data based on .txt In the future, we should have better internal datatypes for this stuff, i.e. instead of gradle: ['yes'] for True, actually use a boolean. For now, make the YAML and JSON metadata produce the same internal data as .txt.
2017-02-23 18:54:33 +01:00
buildjni: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 1.2.6
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- VanillaX86
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
ndk: r10d
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- sed -i -e '/^TARGET/aexit 0' -e 's@\-d \"gradle\/wrapper\"@1@g' ../compile.sh
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
&& ln -s vlc-android/$$VLC$$ ../vlc
rm: []
scandelete: []
scanignore: []
srclibs:
- VLC@d59b81a
subdir: vlc-android
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 1030005
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 1.2.6
eliminate app.builds everywhere, it should be app['Builds'] The .txt format was the last place where the lowercase "builds" was used, this converts references everywhere to be "Builds". This makes it possible to load metadata YAML files with any YAML parser, then have it possible to use fdroidserver methods on that data, like metadata.write_metadata(). The test files in tests/metadata/dump/*.yaml were manually edited by cutting the builds: block and putting it the sort order for Builds: so the contents should be unchanged. ``` sed -i \ -e 's/app\.builds/app.get('Builds', \[\])/g' \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\])/app.get('Builds', \[\])/g" \ -e "s/app\.get('Builds', \[\])\.append/app\['Builds'\].append/g" \ -e "s/app\['builds'\]/app.get('Builds', [])/g" \ */*.* ```
2020-12-09 16:01:21 +01:00
Categories:
- Multimedia
Changelog: ''
CurrentVersion: 1.2.6
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
CurrentVersionCode: 1030005
eliminate app.builds everywhere, it should be app['Builds'] The .txt format was the last place where the lowercase "builds" was used, this converts references everywhere to be "Builds". This makes it possible to load metadata YAML files with any YAML parser, then have it possible to use fdroidserver methods on that data, like metadata.write_metadata(). The test files in tests/metadata/dump/*.yaml were manually edited by cutting the builds: block and putting it the sort order for Builds: so the contents should be unchanged. ``` sed -i \ -e 's/app\.builds/app.get('Builds', \[\])/g' \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\])/app.get('Builds', \[\])/g" \ -e "s/app\.get('Builds', \[\])\.append/app\['Builds'\].append/g" \ -e "s/app\['builds'\]/app.get('Builds', [])/g" \ */*.* ```
2020-12-09 16:01:21 +01:00
Description: 'Video and audio player that supports a wide range of formats,
for both local and remote playback.
[http://git.videolan.org/?p=vlc-ports/android.git;a=blob_plain;f=NEWS NEWS]
'
Disabled: null
Donate: http://www.videolan.org/contribute.html#money
FlattrID: null
IssueTracker: http://www.videolan.org/support/index.html#bugs
Liberapay: null
License: GPL-3.0-only
Litecoin: null
MaintainerNotes: 'Instructions and dependencies here: http://wiki.videolan.org/AndroidCompile
see http://buildbot.videolan.org/builders/ for version code scheme
The VLC srclib commit can be found out from TESTED_HASH value in compile.sh
On new releases remove the updatecheck and force the CV to the last working
build. This will make sure users don''t get notified about the update until
the final build from the BS has been reviewed and tested. Once done, undo
those changes.
'
Name: null
NoSourceSince: ''
OpenCollective: null
Provides: null
Repo: git://git.videolan.org/vlc-ports/android.git
RepoType: git
RequiresRoot: false
SourceCode: http://git.videolan.org/?p=vlc-ports/android.git;a=summary
Summary: Media player
Translation: ''
UpdateCheckData: null
UpdateCheckIgnore: null
UpdateCheckMode: Tags
UpdateCheckName: null
change VercodeOperation to TYPE_LIST
2022-10-27 13:11:37 +02:00
VercodeOperation:
update test_read_metadata to use ruamel.yaml and YAML 1.2 I tried to get this to indent the .yaml files properly so yamllint defaults work with tests/metadata/dump/*.yaml, but it didn't take for some reason: yaml.indent(mapping=4, sequence=4, offset=2)
2023-05-02 10:59:53 +02:00
- '%c + 5'
eliminate app.builds everywhere, it should be app['Builds'] The .txt format was the last place where the lowercase "builds" was used, this converts references everywhere to be "Builds". This makes it possible to load metadata YAML files with any YAML parser, then have it possible to use fdroidserver methods on that data, like metadata.write_metadata(). The test files in tests/metadata/dump/*.yaml were manually edited by cutting the builds: block and putting it the sort order for Builds: so the contents should be unchanged. ``` sed -i \ -e 's/app\.builds/app.get('Builds', \[\])/g' \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\])/app.get('Builds', \[\])/g" \ -e "s/app\.get('Builds', \[\])\.append/app\['Builds'\].append/g" \ -e "s/app\['builds'\]/app.get('Builds', [])/g" \ */*.* ```
2020-12-09 16:01:21 +01:00
WebSite: http://www.videolan.org/vlc/download-android.html
added: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
id: org.videolan.vlc
rename lastupdated to lastUpdated to match fdroid client This lets index-v1 be parsed directly into class instances because the field/instance var names match exactly. The original index v0 element must retain the 'lastupdated' name for backwards compatibility.
2016-11-28 21:17:22 +01:00
lastUpdated: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
metadatapath: metadata/org.videolan.vlc.yml
Copy Permalink