Mailinglist Archive: opensuse-packaging (97 mails)

< Previous Next >
Re: [opensuse-packaging] On how to improve Rust packaging experience for suse

On 20 Nov 2019, at 05:57, John Paul Adrian Glaubitz
<adrian.glaubitz@xxxxxxxx> wrote:

On 11/19/19 7:15 PM, Jan Engelhardt wrote:
An alternative would be to devote the manned resources to not grow minute
dependencies on large stacks. (That ship has probably sailed in terms of
firefox-in-the-distro, (...)

Unless Firefox has changed since the last time I touched the codebase, I'm
pretty sure that it has all the Rust crates vendored which it needs. So,
Firefox alone shouldn't be a problem.

I think Rust projects will always tend to vendoring, because the huge
micro-dependency style system that exists means we'll never keep up trying to
package these. Kanidm has ~200 crate indirect dependencies on it's own, I can't
imagine how many firefox has. It's a waste of our time to try to package all
200 when we could be putting that time into other things instead. This
essentially means we are always at the whims of those vendored dependencies and
what they require, and that is highly likely to be the "latest" stable compiler.

I think we should aim to:

* Have rustc/cargo move with the upstream cadence, with automation as suggested
into all SLE/LEAP/TW/Other
* Do not attempt to package crates - only package leaves IE consuming projects
* Improve our rust macros and packaging guides around this topic.

As much as we want to wring our hands and slow down rust, and do things "our
way" we can't - we have to follow and adapt in this case.

So where do we start to start to achieve this?



William Brown

Senior Software Engineer, 389 Directory Server

To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >