From: EuAndreh <eu@euandre.org>
To: andi@notmuch.email, ~euandreh/public-inbox@lists.sr.ht
Cc: 
Subject: Re: crate2nix
In-Reply-To: <20201006075258.52tz5u5a36fpbfwy@wrt>
References: <20201006075258.52tz5u5a36fpbfwy@wrt>
Date: Tue, 06 Oct 2020 06:09:27 -0300
Message-ID: <87r1qbafg8.fsf@euandre.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

andi@notmuch.email writes:

> Hi,

Hi there!

> Just saw your crate2nix code and it looks very nice and clean!

=E2=98=BA=EF=B8=8F

> Just a heads-up, since you might not aware of all the alternatives out
> there, there is a version from Eelco that basically does the same as
> yours but also handles git dependencies. I did blog about that briefly
> last month [1].

I wasn't aware of it. At a first glance, it looks remarkably similar!
Maybe I'm on to something =F0=9F=98=AC. I'll try it later, thanks for the l=
inks.

> I am curious if you were aware of that and/or naersk [2] as both of them
> also come with the promise of no generated files and no *2nix commands
> to execute.

I did try naersk. It was the best one I found, in fact. It does use
Cargo under the hood to drive things, but it doesn't expose the
environment it builds. With it you can parameterize the Cargo commands,
but not run it by yourself.

In fact, there's a snippet that I copied directly from naersk[0]. I
didn't mention it on the README, only on the commit log.

[0]: https://git.euandreh.xyz/cargo2nix/commit/?id=3Dc75e7e2d3ee7f7e074ea9f=
8e5b959d6395338acc