Re: Building "cargo-c": over 400 packages to be downloaded?
"Bruce Dubbs" ([email protected] via blfs-support Mailing List) <[email protected]> Thu, 12 Mar 2026 11:52:32 -0500
| Newsgroups | gmane.linux.lfs.beyond.support |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1773334364-15154-15007 Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 3/12/26 5:28 AM, Rainer Fiebig ([email protected] via blfs-support Mailing List) wrote: > "Cargo-c" is required for later versions of librsvg which I wanted to > update for security-reasons (SA 12.4 098). > > An offline-build of cargo-c doesn't seem possible and the download of > file "cargo.lock" is necessary. I checked version -0.10.21 of that file > and it has over 400 "package" sections, all with name and url: > > /usr/src> grep -c 'package' Cargo.lock-0.10.21 > 417 > > Before I actually initiate the build (if at all): are really over 400 > obscure packages downloaded during the build without any control by the > user? Thanks. Yes, they are "needed", but I don't like it either. I think the rust/cargo build process needs to be re-thought. -- Bruce ------------=_1773334364-15154-15007 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 -- http://lists.linuxfromscratch.org/sympa/info/blfs-support Unsubscribe: See the above information page ------------=_1773334364-15154-15007--