7cd1ea31e4
Author: Tom Marshall <tdm.code@gmail.com>
Date: Wed Oct 25 20:27:08 2017 +0200
Revert "kill package_extract_dir"
changes for P:
- bring back the mkdir_recursively variant which takes a timestamp.
- add libziparchive dependency
- fix otautil header paths
changes for Q:
- change ziputil naming convention to lowercase
This reverts commit 53c38b15381ace565227e49104a6fd64c4c28dcc.
Change-Id: I71c488e96a1f23aace3c38fc283aae0165129a12
Author: Tom Marshall <tdm.code@gmail.com>
Date: Thu Dec 14 22:37:17 2017 +0100
Revert "Remove the obsolete package_extract_dir() test"
This reverts commit bb7e005a7906b02857ba328c5dfb11f1f3cb938e.
Change-Id: I643235d6605d7da2a189eca10ec999b25c23e1f9
Author: Tom Marshall <tdm.code@gmail.com>
Date: Wed Aug 23 18:14:00 2017 +0000
Revert "updater: Remove some obsoleted functions for file-based OTA."
This reverts commit 63d786cf22cb44fe32e8b9c1f18b32da3c9d2e1b.
These functions will be used for third party OTA zips, so keep them.
Change-Id: I24b67ba4c86f8f86d0a41429a395fece1a383efd
Author: Stricted <info@stricted.net>
Date: Mon Mar 12 18:11:56 2018 +0100
recovery: updater: Fix SymlinkFn args
Change-Id: If2ba1b7a8b5ac471a2db84f352273fd0ea7c81a2
Author: Simon Shields <simon@lineageos.org>
Date: Thu Aug 9 01:17:21 2018 +1000
Revert "updater: Remove dead make_parents()."
This reverts commit 5902691764e041bfed8edbc66a72e0854d18dfda.
Change-Id: I69eadf1a091f6ecd45531789dedf72a178a055ba
Author: Simon Shields <simon@lineageos.org>
Date: Thu Aug 9 01:20:40 2018 +1000
Revert "otautil: Delete dirUnlinkHierarchy()."
changes for P:
- Fix missing PATH_MAX macro from limits.h
This reverts commit 7934985e0cac4a3849418af3b8c9671f4d61078a.
Change-Id: I67ce71a1644b58a393dce45a6c3dee97830b9ee4
Author: XiNGRZ <chenxingyu92@gmail.com>
Date: Tue Dec 3 14:31:56 2019 +0800
updater: Fix lost capabilities of set_metadata
This was broken since Android O. During a file-based incremental OTA,
capability flags were cleared but not being set again properly, leading
some critical processes (e.g. surfaceflinger and pm-service) fails.
For more details, see:
|
||
---|---|---|
.. | ||
include/edify | ||
Android.bp | ||
expr.cpp | ||
lexer.ll | ||
parser.yy | ||
README.md | ||
yydefs.h |
edify
Update scripts (from donut onwards) are written in a new little scripting language ("edify") that is superficially somewhat similar to the old one ("amend"). This is a brief overview of the new language.
-
The entire script is a single expression.
-
All expressions are string-valued.
-
String literals appear in double quotes. \n, \t, ", and \ are understood, as are hexadecimal escapes like \x4a.
-
String literals consisting of only letters, numbers, colons, underscores, slashes, and periods don't need to be in double quotes.
-
The following words are reserved:
if then else endif
They have special meaning when unquoted. (In quotes, they are just string literals.)
-
When used as a boolean, the empty string is "false" and all other strings are "true".
-
All functions are actually macros (in the Lisp sense); the body of the function can control which (if any) of the arguments are evaluated. This means that functions can act as control structures.
-
Operators (like "&&" and "||") are just syntactic sugar for builtin functions, so they can act as control structures as well.
-
";" is a binary operator; evaluating it just means to first evaluate the left side, then the right. It can also appear after any expression.
-
Comments start with "#" and run to the end of the line.
Some examples:
-
There's no distinction between quoted and unquoted strings; the quotes are only needed if you want characters like whitespace to appear in the string. The following expressions all evaluate to the same string.
"a b" a + " " + b "a" + " " + "b" "a\x20b" a + "\x20b" concat(a, " ", "b") "concat"(a, " ", "b")
As shown in the last example, function names are just strings, too. They must be string literals, however. This is not legal:
("con" + "cat")(a, " ", b) # syntax error!
-
The ifelse() builtin takes three arguments: it evaluates exactly one of the second and third, depending on whether the first one is true. There is also some syntactic sugar to make expressions that look like if/else statements:
these are all equivalent
ifelse(something(), "yes", "no") if something() then yes else no endif if something() then "yes" else "no" endif
The else part is optional.
if something() then "yes" endif # if something() is false, # evaluates to false
ifelse(condition(), "", abort()) # abort() only called if # condition() is false
The last example is equivalent to:
assert(condition())
-
The && and || operators can be used similarly; they evaluate their second argument only if it's needed to determine the truth of the expression. Their value is the value of the last-evaluated argument:
file_exists("/data/system/bad") && delete("/data/system/bad")
file_exists("/data/system/missing") || create("/data/system/missing")
get_it() || "xxx" # returns value of get_it() if that value is # true, otherwise returns "xxx"
-
The purpose of ";" is to simulate imperative statements, of course, but the operator can be used anywhere. Its value is the value of its right side:
concat(a;b;c, d, e;f) # evaluates to "cdf"
A more useful example might be something like:
ifelse(condition(), (first_step(); second_step();), # second ; is optional alternative_procedure())