Re: Split Packages files based on new section "buildlibs"
On 11/11/20 8:37 PM, Russ Allbery wrote:
> Simon McVittie <smcv@debian.org> writes:
>> My understanding is that Rust and Go code literally doesn't have
>> analogous built-in system-wide search paths for third-party libraries,
>> and when building Debian packages that contain Rust and Go code, we have
>> to invent them in a Debian-specific way.
>
> Rust and Go both vendor dependencies during their build. Python isn't
> really analogous; you *can* do something similar with virtualenvs, but (a)
> Python doesn't really have a build the way that Rust and Go do because one
> generally doesn't produce native code, and (b) the virtualenv approach is
> optional and only one of many ways of assembling Python applications,
> whereas there's largely only one way Rust and Go binaries are built.
No, a lot of python projects do vendoring like Rust and Go. That's different
than a virtualenv. Usually you have a sub-package called vendor or _vendor in
the package namespace.
Matthias
Reply to: