From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 42734@debbugs.gnu.org
Subject: [bug#42734] Export android-platform-system-core
Date: Mon, 10 Aug 2020 05:46:08 +0200 [thread overview]
Message-ID: <20200810054608.511a3dd9@primarylaptop.localdomain> (raw)
In-Reply-To: <20200810052750.23795deb@primarylaptop.localdomain>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Mon, 10 Aug 2020 05:27:50 +0200
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> One way of doing that would be to create an android-system-core-header
> package and reference that.
>
> Does that look like a good idea?
I keep sending mails too fast.
Inside the tarball we have:
> $ ls include/
> android backtrace binderwrapper cutils diskconfig log memtrack
> mincrypt nativebridge netutils private system sysutils usbhost
> utils ziparchive
So that could be spitted somehow.
For instance include/log/ would be packaged in android-liblog for
instance.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-10 3:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 0:44 [bug#42734] Export android-platform-system-core Denis 'GNUtoo' Carikli
2020-08-07 2:10 ` [bug#42734] [PATCH 1/2] gnu: android: Export android-platform-version Denis 'GNUtoo' Carikli
2020-08-07 2:10 ` [bug#42734] [PATCH 2/2] gnu: android: Export android-platform-system-core Denis 'GNUtoo' Carikli
2020-08-07 8:24 ` bug#42734: [PATCH 1/2] gnu: android: Export android-platform-version Mathieu Othacehe
2020-08-07 11:33 ` [bug#42734] Export android-platform-system-core Julien Lepiller
2020-08-10 3:19 ` Denis 'GNUtoo' Carikli
2020-08-10 3:27 ` Denis 'GNUtoo' Carikli
2020-08-10 3:46 ` Denis 'GNUtoo' Carikli [this message]
2020-08-10 13:50 ` Julien Lepiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200810054608.511a3dd9@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=42734@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.