Re: Proposing new ostreedev/ Rust repositories: ostree-ext and ostree-container

[Felix Krull <f_krull gmx de>]

Yeah, I am subscribed to the list, just didn't get around to
replying/putting my thoughts in order.

Just from an organisational perspective, I'm all for moving the Rust
bindings into the OSTree organisation (such as it is), whether as a
separate repo under github.com/ostreedev or as part of a future
monorepo. With official parts of OSTree being written in Rust and
using the Rust bindings -- as well as rpm-ostree -- I'm not keen on
being stuck in the middle of that with my essentially-personal
project. I can very much do without the pressure and expectations that
come from that. :)

On Tue, 6 Apr 2021 at 00:18, Colin Walters <walters verbum org> wrote:
> A more aggressive version is (and this would require Felix's buy-in) merging crates.io/crates/ostree with 
> ostree-ext and ostree-container so we have
>
> github.com/ostreedev/ostree (as it exists today)
> github.com/ostreedev/ostree-rs

I'm mostly in favour of keeping the ostree and ostree-ext crates
separate. ostree-rs is mostly gir-generated code which brings its own
limitations (for example, the crate is still Rust 2015 because the
generated code doesn't compile with 2018). Putting significant
additional functionality in there might be awkward. And given that
cargo exists, there's no strong reason to merge them IMO other than
picking appropriate names.

But obviously I'm in favour of more Rust in general. :D