Ubuntu
android-platform-external-boringssl package

android-platform-external-boringssl 13.0.0+r11-2 source package in Ubuntu

Changelog

android-platform-external-boringssl (13.0.0+r11-2) unstable; urgency=medium

  * debian/rules: Export gdwarf-4 so we align with ubuntu patches.

 -- Roger Shimizu <email address hidden>  Tue, 15 Nov 2022 22:28:07 -0800

Upload details

Uploaded by:
Android tools Maintainer
Uploaded to:
Sid
Original maintainer:
Android tools Maintainer
Architectures:
armel armhf arm64 amd64 i386 ppc64el mipsel mips64el hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 riscv64 sh4 x32
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
android-platform-external-boringssl_13.0.0+r11-2.dsc 3.0 KiB 9aecd39a360252b6f6c43b11cfee1012a5a964bef1be44db95ef282f9acb1bce
android-platform-external-boringssl_13.0.0+r11.orig.tar.xz 28.1 MiB 202dd292e8041f670628fa49fcde164e60f0fec20c7fd0b9b66b1112852a579b
android-platform-external-boringssl_13.0.0+r11-2.debian.tar.xz 15.3 KiB b111faab5b7b14cd2dba13f77ae5c9f93a5f55a6bbc62f7a77e2cb294a1244b0

No changes file available.

Binary packages built by this source

android-boringssl: Google's internal fork of OpenSSL for the Android SDK - tool

 The Android SDK builds against a static version of BoringSSL,
 Google's internal fork of OpenSSL. This package should never be used
 for anything but Android SDK packages that already depend on it.
 .
 BoringSSL arose because Google used OpenSSL for many years in various
 ways and, over time, built up a large number of patches that were
 maintained while tracking upstream OpenSSL. As Google’s product
 portfolio became more complex, more copies of OpenSSL sprung up and
 the effort involved in maintaining all these patches in multiple
 places was growing steadily.
 .
 This is the Android AOSP fork of BoringSSL which is designed to be
 used by Android and its SDK. BoringSSL is only ever statically linked
 into apps, and pinned to a commit version. Upstream has no official
 releases of BoringSSL on its own, so it must be included separately
 for each project that uses it.
 .
 This package contains the boringssl command line tool.

android-boringssl-dbgsym: debug symbols for android-boringssl
android-libboringssl: Google's internal fork of OpenSSL for the Android SDK

 The Android SDK builds against a static version of BoringSSL,
 Google's internal fork of OpenSSL. This package should never be used
 for anything but Android SDK packages that already depend on it.
 .
 BoringSSL arose because Google used OpenSSL for many years in various
 ways and, over time, built up a large number of patches that were
 maintained while tracking upstream OpenSSL. As Google’s product
 portfolio became more complex, more copies of OpenSSL sprung up and
 the effort involved in maintaining all these patches in multiple
 places was growing steadily.
 .
 This is the Android AOSP fork of BoringSSL which is designed to be
 used by Android and its SDK. BoringSSL is only ever statically linked
 into apps, and pinned to a commit version. Upstream has no official
 releases of BoringSSL on its own, so it must be included separately
 for each project that uses it.

android-libboringssl-dbgsym: debug symbols for android-libboringssl
android-libboringssl-dev: Google's internal fork of OpenSSL for the Android SDK - devel

 The Android SDK builds against a static version of BoringSSL,
 Google's internal fork of OpenSSL. This package should never be used
 for anything but Android SDK packages that already depend on it.
 .
 BoringSSL arose because Google used OpenSSL for many years in various
 ways and, over time, built up a large number of patches that were
 maintained while tracking upstream OpenSSL. As Google’s product
 portfolio became more complex, more copies of OpenSSL sprung up and
 the effort involved in maintaining all these patches in multiple
 places was growing steadily.
 .
 This is the Android AOSP fork of BoringSSL which is designed to be
 used by Android and its SDK. BoringSSL is only ever statically linked
 into apps, and pinned to a commit version. Upstream has no official
 releases of BoringSSL on its own, so it must be included separately
 for each project that uses it.
 .
 This package contains the development files.