From: swedebugia <swedebugia@riseup.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>, guix-devel <guix-devel@gnu.org>
Subject: Re: Go importer - help with git-fetch
Date: Tue, 6 Aug 2019 14:45:37 +0200 [thread overview]
Message-ID: <b03263f0-5927-d415-533e-5604bf71d7cb@riseup.net> (raw)
In-Reply-To: <87sgqezj1p.fsf@ambrevar.xyz>
On 2019-08-06 12:26, Pierre Neidhardt wrote:
> Just to be sure: did you write the go imported from scratch? Because a
> work-in-progress has been available for a while, you may want to base
> your work on it.
Oh. Yeah, I did based on Go-Search and with inspiration from Jakob Kreuze.
I just found the WIP golang.scm among the patches, see #35627. It relies
on unstable github tarballs for sha256 hashes which in my view is not a
viable approach. Also it was lacking an easy road to recursive import
which is really what we want IMHO.
My patch is quite concise in comparison and also extract licenses and
readme's from github. It also has a complete list of the dependencies
and can be easily extended with recourse-ability.
Only the hashing is missing now, besides the calling script in
guix/scripts/import and documentation.
Anyone know how to calculate the hash based on a checkout?
--
Cheers Swedebugia
next prev parent reply other threads:[~2019-08-06 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 10:23 Go importer - help with git-fetch swedebugia
2019-08-06 10:26 ` Pierre Neidhardt
2019-08-06 12:45 ` swedebugia [this message]
2019-08-06 12:56 ` Ricardo Wurmus
2019-08-06 13:04 ` Jakob L. Kreuze
2019-08-06 20:26 ` swedebugia
2019-08-06 20:46 ` Jakob L. Kreuze
2019-08-06 22:02 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b03263f0-5927-d415-533e-5604bf71d7cb@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).