Lines Matching +full:ship +full:- +full:to
3 # Use of this source code is governed by a BSD-style license that can be
9 supported app with the highest version code to devices. Note that Play Store
17 versions of a package. Without unique codes, promoting a beta apk to stable
28 TrichromeLibrary when these are compiled to use the stable package name. Similar
29 to how WEBVIEW_STABLE/WEBVIEW_BETA work, this allows users to opt into the open
30 Beta Track for the stable package. When Trichrome is configured to use a
65 This ensures that they are considered "newer" than any non-next build of the
72 """List of version numbers to be created for each build configuration.
77 Here, (supported ABIs) is referring to the combination of browser ABI and
79 64-bit browser with an extra 32-bit Webview library. See also
136 # Splits input build config architecture to manufacturer and bitness.
140 # Until riscv64 needs a unique version code to ship APKs to the store,
141 # point to the 'arm' bitmask.
147 # Expose the available choices to other scripts.
160 - All production arm64 devices can also run arm
161 - All production x64 devices can also run x86
162 - Pretty much all production x86/x64 devices can also run arm (via a binary
165 Since the Play Store has no particular preferences, you have to encode your own
169 - For any android app, it's theoretically preferable to ship a 64-bit version to
170 64-bit devices if it exists, because the 64-bit architectures are supposed to
171 be "better" than their 32-bit predecessors (unfortunately this is not always
172 true due to the effect on memory usage, but we currently deal with this by
173 simply not shipping a 64-bit version *at all* on the configurations where we
174 want the 32-bit version to be used).
175 - For any android app, it's definitely preferable to ship an x86 version to x86
178 - For WebView, Monochrome, and Trichrome specifically, they are a special class
179 of APK called "multiarch" which means that they actually need to *use* more
181 more than one). The 64-bit builds of these multiarch APKs contain both 32-bit
182 and 64-bit code, so that Webview is available for both ABIs. If you're
183 multiarch you *must* have a version that supports both 32-bit and 64-bit
184 version on a 64-bit device, otherwise it won't work properly. So, the 64-bit
185 version needs to be a higher versionCode, as otherwise a 64-bit device would
186 prefer the 32-bit version that does not include any 64-bit code, and fail.
194 so arm codes must be lower than x86 codes to prevent providing an
195 arm-optimized build to intel devices.
198 A dictionary of architecture mapped to bitness
199 mapped to version code suffix.
201 # Scheme change was made directly to M113 and M114 branches.
248 """Translates a version code to its component parts.
251 A 5-tuple (VersionCodeComponents) with the form:
252 - Build number - integer
253 - Patch number - integer
254 - Package name - string
255 - ABI - string : if the build is 32_64 or 64_32 or 64, that is just
256 appended to 'arm' or 'x86' with an underscore
257 - Whether the build is a "next" build - boolean
270 patch_number_plus_extra = int(version_code[-5:])
273 patch_number_plus_extra -= _NEXT_BUILD_VERSION_CODE_DIFF
278 abi_digit = int(version_code[-1])
279 package_digit = int(version_code[-2])
281 abi_digit = int(version_code[-2])
282 package_digit = int(version_code[-1])
284 # Before branch 4844 we added 5 to the package digit to indicate a 'next'
288 package_digit -= 5
322 - MINOR is always 0. It was used for something long ago in Chrome's history
324 - MAJOR is cosmetic and controlled by the release managers. MAJOR and BUILD
361 parser.add_argument('--webview',