Ubuntu
android-platform-external-boringssl package

android-platform-external-boringssl 14.0.0+r11-4 source package in Ubuntu

Changelog

android-platform-external-boringssl (14.0.0+r11-4) unstable; urgency=medium

  * debian/control: Remove android-boringssl package for hurd-*.

 -- Roger Shimizu <email address hidden>  Sun, 12 Nov 2023 01:07:44 -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 alpha arc hurd-amd64 hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 loong64 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_14.0.0+r11-4.dsc 4.0 KiB 8ed31e1c1ec9a48702835674f44558ebdb571f1c01e9772f8a9d65d57116490a
android-platform-external-boringssl_14.0.0+r11.orig.tar.xz 30.3 MiB 9d4851f48b1178596fec3b4f8a1394020ee1d64e713853ae42dd60ca5abb080b
android-platform-external-boringssl_14.0.0+r11-4.debian.tar.xz 26.6 KiB a3ad9cb1c0e4d50f949c21a0bc702b87417b5fa8c1d05f72ebe451205461cbe4

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.