Re: ostree oxidation: internal components written in Rust

The GObject API would still be provided right?

Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else

On Tue, Dec 18, 2018, 11:29 AM Luca BRUNO <lucab lucabruno net wrote:
Hi all,
This is a followup to a discussion which started on this Github PR:

ostree currently ships some internal components written in Rust,
which can be opted-in at configure time[0].

I've recently seen an increasing interest around using Rust in
Gnome-land, and I think there are a few ostree pieces which could
be good targets for that as well.

However the current approach of maintaining parallel (C and Rust)
implementations of everything is not very appealing.
There are precedents of related projects (rpm-ostree[1] and librsvg[2])
which are now hard-requiring a rustc+cargo toolchain, which would help
reducing the configuration matrix.

What would be the general (developers, maintainers, and users) feedback
to proposing a similar move for ostree? Would it be feasible in the
near future to unconditionally required `--enable-rust` (and to drop
the configuration option)?


Ciao, Luca

"If you build a wall, think of what you leave outside it" - Italo Calvino

ostree-list mailing list
ostree-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]