Re: Using 3rd party crates in an out-of-tree module

["Nándor Krácser" <bonifaido@gmail.com>]

Currently I'm experimenting with different crates which I would like
to use in my module, serialization libraries, math libraries. etc,
even complex ones, are really hard to pull in as a direct source
library (copy the code to the module), and if they have a transitive
dependency that complicates things even more.

I totally agree, that submitting something to the mainline with
libraries linked out there in the "wild" makes them hard to merge,
however a kernel crate sounds really good and is a bit more native to
rust.

Regards,
Nandor

On Tue, Mar 22, 2022 at 12:15 AM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Mon, Mar 21, 2022 at 10:17 PM Alex Gaynor <alex.gaynor@gmail.com> wrote:
> >
> > I don't know if anyone has given any thought to supporting 3rd party
> > crates for out-of-tree modules.
>
> It is possible that we will have some form of dependency support
> within the kernel (e.g. to split the `kernel` crate), which could be
> used by out-of-tree modules too.
>
> Extending this to Cargo-based crates could be possible, but we would
> need a clear use case -- if an out-of-tree module requires a
> third-party crate, it is fairly likely others in-tree also need the
> same problem solved. It can also complicate submitting the out-of-tree
> module later on to mainline if one relied on third-party code which
> now has an alternative in-tree.
>
> Cheers,
> Miguel



-- 
Krácser Nándor István
bonifaido@gmail.com