floss.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
For people who care about, support, and build Free, Libre, and Open Source Software (FLOSS).

Administered by:

Server stats:

685
active users

Wanted to run your own builder for and were disappointed our RBuilder Setup was only available for Debian-based systems? Then we have good news for you: a few min ago, 2 PRs have been merged. The setup scripts now also support RPM & Arch based systems 🥳

RPM/Arch lack packages for apksigner & dexdiff (which are needed for debugging). We're on it, those will follow hopefully soon™.

Thanks to @Iamlooker and Patrick (from FlorisBoard) for your help!

codeberg.org/IzzyOnDroid/rbuil

Codeberg.orgrbuilder_setupScripts to automate setup of rbtlog, rbhelper, and their dependencies

@IzzyOnDroid @Iamlooker Are there sane AUR packages for the missing Arch dependencies? If so I can probably sponsor them moving to official repos.

@alerque @IzzyOnDroid apksigner and dexdump are part of android-sdk-build-tools package on AUR. They are up-to-date and running perfectly

@Iamlooker @IzzyOnDroid

This package is incorrectly named because it doesn't build from sources, just repackages upstream built sources—it should be -bin. If I were to put something in official repos it would have to be a source build. Is building these from sources possible?

In the mean time that bin package is built and hosted in my unofficial user repo, but signed with official keys:

wiki.archlinux.org/title/Unoff

So adding that to a repo collection would be a low friction way to get setup.

wiki.archlinux.orgUnofficial user repositories - ArchWiki
IzzyOnDroid ✅

@alerque which one is "this"? I'm unsure if it would be a good idea to pull in the entire build tools package just for dexdump and apksigner. But I must admit I didn't check how much overhead that means. So as it's not essential for *running* a builder, it's just mentioned as a manual install option for now. But if the overhead is small enough, or if there were separate package(s) for those two, that could be included in the default install of course. @Iamlooker

@IzzyOnDroid @Iamlooker android-sdk-build-tools should be android-sdk-build-tools-bin. Except in special cases upstream generated binaries are not eligible for official packaging, we need to be able to build from source. The AUR allows such recipes that fetch and wrap upstream but they should have bin suffixes on the package names.

Are dexdump and apksigner sources available? Do they have some sort of stable versioning scheme that applies to them upstream?

@IzzyOnDroid @Iamlooker At first blush packaging those each separately as stand alone tools looks doable. Is there a specific series of tags it would be most useful to follow? Remember Arch is rolling release and we can only (easily) have one latest release at a time.

Thanks @alerque! I'm not that familiar with their WebIf, but at least for apksig they show some tags on the left pane; picking the latest android-*-r* one (currently android-15.0.0_r23, visible after following the "More..." link) should be fine. Same tags are on the art repo where dexdump is in. @Iamlooker

@alerque @IzzyOnDroid Yes, they can be built from source butI have no experience with using pkgbuild for compilation.
And yes theyhave a stable versioning scheme which is the official versioning of Android SDK