atisfied with how easy it is, and I think Guix could benefit a
lot by adopting a similar approach.
What am I missing here? Are there any disavantages to this approach?
Anything that would break from it if adopted on Guix?
Any questions or suggestions?
Murilo
[1]
https://codebe
--
Best regards,
Murilo
ne.
No need to edit '.guix-authorizations'.
It also works for authenticated channel forks, you just need to add your key to
the 'keyring' branch of the channel fork and it will work.
Just sharing this quick hack I use, its far from ideal but it works for me, and
seeing this dis
and use regular package
inputs, as Efraim noted.
I might be mistaken but I believe the new 'zig-build-system' does something
similar to how cargo works when building, and it used to have #:zig-inputs
in the WIP implementation which was rewritten later as regular input fields,
perhaps we could do some analogous work for 'cargo-build-system'.
Best regards,
Murilo
On Wed Feb 26, 2025 at 12:30 PM -03, Efraim Flashner wrote:
> I was looking closely at cargo2guix earlier this week, and I hacked up
> that if a [[package]] had a source but no checksum it was a git
> reference, and if it had no source and no checksum then it must be
> inside the workspace.
Yes, t
On Wed Feb 26, 2025 at 3:43 AM -03, Hilton Chain wrote:
> Time to try in your own channel!!!
I just did, it worked for helix. I'll be trying in some more rust packages in
the following days.
> * Package cargo-audio[1] and cargo-license[2] or similiar software, and write
> a
> step-by-step pack
On Thu Mar 6, 2025 at 2:24 PM -03, Efraim Flashner wrote:
> On Wed, Mar 05, 2025 at 09:20:50PM +0800, Hilton Chain wrote:
>> 1. Unpack package source then update lockfile:
>> --8<---cut here---start->8---
>> cargo generate-lockfile
>> --8<---cut here-
