apt-pkg-native

Go to file

Stefan Reiter 07c92f003b add package detail accessors * short description * long description * maintainer * homepage Requires constructing a pkgRecords::Parser to read for some reason. AFAICT this parser is bound to the pkgRecords instance and deleted together with it, so it doesn't require an explicit delete/free.		2020-10-30 00:11:07 +00:00
apt-pkg-c	add package detail accessors	2020-10-30 00:11:07 +00:00
examples	edition = 2018	2019-01-21 22:22:47 +00:00
src	add package detail accessors	2020-10-30 00:11:07 +00:00
.gitignore	list packages (after manual make)	2017-07-12 21:18:34 +01:00
.travis.yml	chore: bump travis	2019-12-29 21:37:25 +00:00
build.rs	hack: work around https://github.com/rust-lang/rust/pull/57018	2019-04-13 23:08:48 +01:00
Cargo.toml	chore: dev itertools -> 0.9	2020-08-20 21:12:39 +01:00
LICENSE.MIT	docs / crates.io stuff	2017-07-13 16:12:58 +01:00
README.md	minor lie in the readme	2019-01-21 22:20:47 +00:00

README.md

This crate provides bindings to libapt-pkg.

Documentation and Examples

See the examples/ folder for some partial implementations of some commands.

https://docs.rs/apt-pkg-native

License Note

While the code in this crate is available under a permissive MIT license, it is useless without libapt-pkg, which is GPL2+.

Building

libapt-pkg-dev must be installed. The cc crate is used to try and find a native compiler.

The ye-olde-apt feature provides support for apt <1.2 (Ubuntu 14.04 (Trusty), Debian 7 (Jessie) (2015)). This works by just deleting methods which are not available in that version. See #2.

Thread safety

It is intended that the crate should be usable from multiple threads. However, this is generally implemented using singletons, which may be really annoying for your use-case.

The current way the singleton is managed is awful, and it's not been fixed while I've been learning about the problems. A major version bump, and a proper singleton, may resolve some of the issues. This needs to be done eventually.

apt does not have a concurrency model: you may not use threads.

Since apt 1.4 or 1.5 (in Debian Stretch (2017), but not in Xenial 16.04), some operations are thread safe: it should be possible to initialise the cache twice in parallel. As these versions of apt are not widespread, the API of this crate does not attempt to expose this.

Switching distro with `docker`

examples/on-sid has a docker file which builds a minimum Debian image with typical package lists downloaded. You can run a tool in it, from this directory, by: