termux / termux-packaging

Termux packaging tools.

This repository has been archived since it is not in use by any of Termux's component

Termux packaging tools

This project contains packaging tools for Termux written in Rust.

NOTE: This is my first Rust code, so suggestions for improvements are very welcome!

NOTE: These are newly created tools not yet tested.

Contributing

Run ./check.sh to format code with rustfmt and check it with clippy before submitting a pull request.

termux-packaging's Issues

lost Cargo.toml

Dear Sir

when i clone this project

and then

run make

or

input { " docker run --rm -it fredrikfornwall/rust-static-builder sh"}

i get

could not find Cargo.toml in /build or any parent directory

THX

Is this normal? (Generating bootstrap zip)

I'm running generate-bootstraps.sh with my parameters: --architectures aarch64 --prefix me.danielrosero.blastergram --repository https://danielroserobintray.bintray.com/blastergram/

Managed to crate an APT repository in bintray, and the script finishes without problem.

But somehow I'm getting a zip without SYMLINKS.txt and only this content inside:

Is this normal?

Thanks for replying.

line 295: declare: -A: invalid option

./generate-bootstraps.sh --prefix /data/data/com.my.package/files/usr
this got me run into this error

line 295: declare: -A: invalid option
declare: usage: declare [-afFirtx] [-p] [name[=value] ...]

Plz help me out of this. I'm not too clear

Packaging 'libc++' failed

When creating package 'libc++', I got following error:

AAPT: error: attribute 'package' in <manifest> tag is not a valid Android package name: 'net.termux.libc++'

Seems that '+' is not valid character in an android package name.

Move away from HashMap use

Not the RustPolice but the thing I see is that the apt_repos.rs Package::fields should be statically defined in a struct with some of them being an Option if needed.

This is the most "unrusty" thing about your code. Using a HashMap like this is whats called "stringly typed" code. It's ignoring the power of the type system to clearly define the state of the data expected to keep the error boundary right at ingestion.

Enforce your error boundary as you ingest data from outside and then inside code can rely on clearly Type facts about the data ingested.

I think if you change that idea in apt_repo.rs the rest of your code will clean up from there.

Try using match against values in the struct further into your code for example.