I'm not sure anyone is using the systemtarball functionality anymore,
especially with the lack of selinux as you've discovered.

Generally we put the prebuilt APKs as inputs into the Android build, since
they may be modified and transformed by the build (uncompress shared libs,
strip dex files, create odex files, do various sanity checks). But there's
a handful of cases where that may not matter and you can post-process them
into a built artifact from a platform build. In that case, you can do
something like:

1. Saving the target-files-package zip and otatools.zip from the Android
platform build. The target-files-package is the input to the OTA scripts,
and is a zip file containing all content and metadata (but not tools,
that's otatools) needed to create an android image. It can contain full
image files as well.

2. Manipulate the zip file to add your APKs to SYSTEM/, and remove any
IMAGES/ files that you want to regenerate.

3. Use the releasetools -- either from build/tools/releasetools and various
built tools, or from otatools.zip to recreate the images:
releasetools/add_img_to_target_files <target-files-package>

- Dan

On Wed, Sep 19, 2018 at 8:20 AM Jan Leonhardt <cyberdesigner....@gmail.com>
wrote:

> Hello yall,
>
> i tried to create a system tarball to add some apk's in other build jobs.
>
> but the created tarballs have no selinux context inside. a look into
> build/tools/mktarball.sh shows, that tar is used without --selinux
> parameter.
>
> If i put the content from that tarball to my system partition, my system
> cant boot, because the contexts for all services are missing.
> If i write the system.img to my system partition, all the contexts are
> there.
>
> i am doing something totally wrong, or should the --selinux param been
> added to mktarball.sh?
>
> thanks in advance!
>
> Jan
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building@googlegroups.com
> To unsubscribe from this group, send email to
> android-building+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the "Android Building" 
mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-building+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to