topgrade VS Cargo

I don't understand why more people aren't aware of this: https://github.com/topgrade-rs/topgrade -I use it for Linux and Windows.

To upgrade all at once I use topgrade.

For what its; worth, I love me some topgrade for keeping my stuff fresh.

$ topgrade Due to a design issue with notify-send it could be that topgrade hangs when it's finished. If this is the case on your system add the --skip-notify flag to the topgrade command or set skip_notify = true in the config file. If you don't want this message to appear any longer set display_preamble = false in the config file. For more information about this issue see https://askubuntu.com/questions/110969/notify-send-ignores-timeout and https://github.com/topgrade-rs/topgrade/issues/288. ── 17:53:16 - System update ──────────────────────────────────────────────────── keine Neuigkeiten Bitte den Sensor des Yubikey berühren :: Paketdatenbanken werden synchronisiert … core ist aktuell extra 8,3 MiB 25,9 MiB/s 00:00 [##############################################################################] 100% multilib ist aktuell arch4edu ist aktuell :: Vollständige Systemaktualisierung wird gestartet … Es gibt nichts zu tun :: Looking for AUR upgrades... :: Looking for devel upgrades... :: Pakete nicht im AUR: gnome-software-packagekit-plugin js78 libsidplay :: als veraltet markiert: authenticator gnome-defaults-list lib32-aom lib32-libdav1d python2 xone-dkms es gibt nichts zu tun Zwischenspeicher-Verzeichnis: /var/cache/pacman/pkg/ :: Möchten Sie ALLE Dateien aus dem Zwischenspeicher entfernen? [j/N] Datenbank-Verzeichnis: /var/lib/pacman/ :: Möchten Sie ungenutzte Repositorien entfernen? [J/n] Ungenutzte Sync-Repositorien werden entfernt … Clone-Verzeichnis: /home/ingo/.cache/paru/clone :: Do you want to clean ALL AUR packages from cache? [j/N]: Diff-Verzeichnis: /home/ingo/.cache/paru/diff :: Alle gespeicherten Diffs entfernen? [J/n]: ── 17:53:25 - Configuration update ───────────────────────────────────────────── ── 17:53:25 - Gnome Shell extensions ─────────────────────────────────────────── () ── 17:53:25 - rustup ─────────────────────────────────────────────────────────── info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu' stable-x86_64-unknown-linux-gnu unchanged - rustc 1.70.0 (90c541806 2023-05-31) info: cleaning up downloads & tmp directories info: self-update is disabled for this build of rustup info: any updates to rustup will need to be fetched with your system package manager ── 17:53:25 - pip3 ───────────────────────────────────────────────────────────── Requirement already satisfied: pip in /usr/lib/python3.11/site-packages (23.1.2) ── 17:53:26 - Node Package Manager ───────────────────────────────────────────── ── 17:53:27 - Yarn Package Manager ───────────────────────────────────────────── ── 17:53:27 - Node Package Manager ───────────────────────────────────────────── ── 17:53:27 - micro ──────────────────────────────────────────────────────────── Checking for plugin updates Nothing to install / update ── 17:53:28 - Flatpak User Packages ──────────────────────────────────────────── Suche nach Aktualisierungen … Nichts zu tun. Nothing unused to uninstall ── 17:53:28 - Flatpak System Packages ────────────────────────────────────────── Suche nach Aktualisierungen … Nichts zu tun. Nothing unused to uninstall ── 17:53:28 - snap ───────────────────────────────────────────────────────────── All snaps up to date. ── 17:53:29 - Firmware upgrades ──────────────────────────────────────────────── Firmware metadata last refresh: 8 Stunden ago. Use --force to refresh again. Geräte mit keinen verfügbaren Firmware-Aktualisierungen: • SSD 860 QVO 2TB • SSD 870 EVO 4TB • ST1000LM035-1RK172 • WDS100T3XHC-00SJG0 No updatable devices ── 17:53:29 - Summary ────────────────────────────────────────────────────────── System update: OK config-update: OK Gnome Shell Extensions: OK rustup: OK pip3: OK micro: OK Flatpak: OK snap: OK Firmware upgrades: OK Pacman backup configuration files found: /etc/pam.d/doas.pacsave /etc/dracut-uefi-hook.conf.pacsave

The ncurses tui is nice, maybe you can make a wrapper with ideas from topgrade and/or Wingetui

You might want to take a look at https://github.com/topgrade-rs/topgrade

Consider adding topgrade. Yeah, I know gnome-software is supposed to be the preferred way now, but I'd still rather update my system from the command line and topgrade will update everything.

Once you have it installations, you can keep it up-to-date with https://github.com/topgrade-rs/topgrade

Installing Trunk happens through Cargo. Remember, Cargo is more than a package manager, it also supports sub-commands.

Dependency Management in Other Languages: We've discussed Python and Node.js in this article, but dependency management is a universal concept in programming. Exploring how you handle dependencies in other languages like Java, C#, or Rust could be beneficial. (I think Rust's cargo is an excellent example of a package manager.)

Nice hack! Would it have been possible back then to use cargo to pull in some dependencies?

The clean solution of cargo script is here: https://github.com/rust-lang/cargo/issues/12207

Yes, I am sure this is going to be a part of Rust 1.77.0 and it will release on 21st March. I say that because of the tag in the PR (https://github.com/rust-lang/cargo/pull/13257#event-11505613...).

I'm no expert on Rust compiler development, but my understanding is that all code that is merged into master is available on nightly. If they're not behind a feature flag (this one isn't), they'll be available in a full release within 12 weeks of being merged. Larger features that need a lot more testing remain behind feature flags. Once they are merged into master, they remain on nightly until they're sufficiently tested. The multi-threaded frontend (https://blog.rust-lang.org/2023/11/09/parallel-rustc.html) is an example of such a feature. It'll remain nightly only for several months.

Again, I'm not an expert. This is based on what I've observed of Rust development.

The author provides very surface-level criticism of two Rust tools, but they don't look into why those choices were made.

With about five minutes of my time, I found out:

wrap_comments was introduced in 2019 [0]. There are bugs in the implementation (it breaks Markdown tables), so the option hasn't been marked as stable. Progress on the issue has been spotty.

--no-merge-sources is not trivial to re-implement [1]. The author has already explained why the flag no longer works -- Cargo integrated the command, but not all of the flags. This commit [2] explains why this functionality was removed in the first place.

Rust is open source, so the author of this blog post could improve the state of the software they care about by championing these issues. The --no-merge-sources error message even encourages you to open an issue, presumably so that the authors of Cargo can gauge the importance of certain flags/features.

You could even do something much simpler, like adding a comment to the related issues mentioning that you ran into these rough edges and that it made your life a little worse, or with a workaround that you found.

Alternatively, you can continue to write about how much free software sucks.

[0]: https://github.com/rust-lang/rustfmt/issues/3347

[1]: https://github.com/rust-lang/cargo/pull/10344

[2]: https://github.com/rust-lang/cargo/commit/3842d8e6f20067f716...

You try to use it as a part of multi-language project, with an external build tool to tie it all together, and you discover that --out-dir flag is still not stabilized over some future compatibility concerns.

To create a new application we'll use cargo (a build tool and also a package manager for Rust. It is used for scaffolding new library/binary projects). So in your projects folder, you can run this command in your terminal:

> ...but at the end of the day Cargo is the reason that Rust is popular.

FWIW, maybe that's true for you, but there are numerous other advantages to the language for which many people choose to use Rust--some even "despite" Cargo: you see Google having had to put in way way WAY too much work to get Bazel working for Rust :/--that it honestly feels a bit like belittling an extremely important language to make this claim so flippantly.

> You can set a default build target for a Cargo project with two lines of configuration, no nightly features necessary...

This doesn't work as, as soon as you start setting target-specific options, it infects the host build, as they incorrectly modelled the problem as some kind of map from targets to flags. If you don't believe me, on your Linux computer, try cross-compile something complicated that will runs on a "least common denominator" Linux distribution, such as CentOS 7.

> Can you clarify what this is referring to?

Sure. I've Googled rust cargo target host bugs for you (which, FWIW, finds a number of bugs I've filed or have talked about, but it isn't as if I have a list anywhere). Note that one of these bugs is "closed", but I still provide them for context as a patch might have been merged but (as you'll find out if you read through all of these) it isn't stable.

https://github.com/rust-lang/cargo/issues/8147

https://github.com/rust-lang/cargo/issues/3349

https://github.com/rust-lang/cargo/pull/9322

https://github.com/rust-lang/cargo/issues/9453

https://github.com/rust-lang/cargo/pull/9753

The result of this work being left incomplete is that increasingly large numbers of "serious" projects--things I'd expect people in packaging land to have heard of, such as BuildRoot--are being forced to set the ridiculous environment variable __CARGO_TEST_CHANNEL_OVERRIDE_DO_NOT_USE_THIS="nightly" in order to get access to a flag that makes Cargo sort of work.

(And yet, I often see people surprised at how long it is taking for various of the more important clients to fully get into using Rust, as the safety issues are so severe from continuing to use C/C++: as you made the contention that you believe the reason why people use Rust is Cargo, I will say the opposite: the reason why we don't see more Rust is also Cargo.)