Creating rust packages drives me crazy.

[crocket]

I am trying to create a package for https://github.com/PirateNetwork/piratepaperwallet

To build this, I need to patch Cargo.toml files and calculate dependencies manually and record the manually calculated dependencies in my ebuild file.

Creating net-p2p/piratewallet-lite::crocket-overlay was a pain in the ass.

Why is it so difficult to create rust packages? Are pirate chain programs exceptions? Or, is it generally frustrating across most rust programs?

[fedeliallalinea]

You can try to use

[Hu]

Rust, like several languages before it, tried to reimplement package management as a language feature. This is generally a bad idea, and especially so when trying to integrate with an existing package manager, such as rpm, apt, or Portage. Having looked at ebuilds for other rust-based projects, it is my opinion that creating packages for Rust projects is generally tedious.

[crocket]

I created net-p2p/piratepaperwallet::crocket-overlay... I got the hang of creating rust packages...

[mustafasalih1993]

addition to fedeliallalinea's reply

if you want to manually create the ebuild without using a tool, you can get the dependencies with the following command

[crocket]

[crocket]

It turns out that `cargo tree --all-features --prefix none` gives me an incomplete dependency list.

cargo-ebuild also gives me an incomplete list.

I had to manually add dependencies from Cargo.lock.

I think I will write Cargo.lock parser in janet language.

[Hu]

[Zucca]

I'm with Hu on this.
On Gentoo, you can expect people having bash (posix also), (g)awk and python of interpreted languages to be installed.
Of course simple C and C++ code can be compiled without extra hassle.
_________________
..: Zucca :..
Gentoo IRC channels reside on Libera.Chat.
--

[mustafasalih1993]

[Hu]

If he writes it in Rust, how could he ever package it? He'd need a package of it before he could package it. I suppose this would follow Rust's pattern though. You must install Rust before you can compile it.

[crocket]

It takes very little time to compile janet. It is very easy to package janet libraries and janet programs. Janet integrates very well with gentoo's packaging system.

I host janet eclasses in my own overlay.

Janet has https://janet-lang.org/docs/peg.html which is better than regular expression. I often use PEG to parse text.

Janet's niche is small-scale system scripting. Parsing text for other packaging systems is a form of system scripting. It's good for creating little utilities.

[mustafasalih1993]

[Hu]

That might be the case, at least for some users, but I could not pass up the opportunity to poke fun at the bootstrapping loop that the Rust project refuses to see as a problem.

[GDH-gentoo]

What I find curious is the event that spawned all this discussion about creating yet another tool: that both dev-util/cargo-ebuild and cargo tree apparently failed to produce a complete list of dependencies for at least one package. I don't do Rust, but it would be interesting to know how did that happen here.

[Goverp]

[mv]

[crocket]

Ideally, Assembly -> C -> Rust -> Other higher-level languages like janet

[mikb]