mirror of
https://github.com/f-droid/fdroidserver.git
synced 2025-11-15 19:50:29 +03:00
Metadata parsing changes
A few small changes to the format of metadata files: "Build Version" lines can now contain include commas by escaping them with a backslash. They can also be split over multiple lines by ending each line (except the last) with a backslash. Additionally, empty lines in descriptions should now work correctly.
This commit is contained in:
parent
09c5c50993
commit
bce5da2543
2 changed files with 140 additions and 119 deletions
11
README
11
README
|
|
@ -169,9 +169,14 @@ configuration to the build. These are:
|
|||
the SDK's ant rules, and forces the Java compiler to interpret
|
||||
source files with this encoding. If you receive warnings during
|
||||
the compile about character encodings, you probably need this.
|
||||
prebuild=xxxx Specifies a shell command (or commands - chain with &&) to run
|
||||
before the build takes place - the only proviso being that you
|
||||
can't use commas in the command.
|
||||
|
||||
prebuild=xxxx Specifies a shell command (or commands - chain with &&) to
|
||||
run before the build takes place. Backslash can be used
|
||||
as an escape character to insert literal commas, or as the
|
||||
last character on a line to join that line with the next.
|
||||
They have no special meaning in other contexts; in
|
||||
particular, literal backslashes should not be escaped.
|
||||
|
||||
novcheck=yes Don't check that the version name and code in the resulting apk
|
||||
are correct by looking at the build output - assume the metadata
|
||||
is correct. This takes away a useful level of sanity checking, and
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue