From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: guix-devel@gnu.org
Subject: Re: getting started with the texlive importer
Date: Wed, 09 Sep 2020 12:53:11 +0100 [thread overview]
Message-ID: <04eeb383787339369224b9a8ad5e568eaa5cc6e6.camel@tourbillion-technology.com> (raw)
Hi Guix,
I have been able to run the texlive importer after making some changes
to guix/import/texlive.scm:
@@ -148,20 +148,22 @@ expression describing it."
((lst ...) (map string->license lst))))
(home-page (string-append "http://www.ctan.org/pkg/" id))
(ref (texlive-ref component id))
- (checkout (download-svn-to-store store ref)))
+ ;; (checkout (download-svn-to-store store ref))
+ )
`(package
(name ,(guix-name component id))
(version ,version)
(source (origin
(method svn-fetch)
(uri (texlive-ref ,component ,id))
- (sha256
- (base32
- ,(bytevector->nix-base32-string
- (let-values (((port get-hash) (open-sha256-
port)))
- (write-file checkout port)
- (force-output port)
- (get-hash)))))))
+ ;; (sha256
+ ;; (base32
+ ;; ,(bytevector->nix-base32-string
+ ;; (let-values (((port get-hash) (open-sha256-
port)))
+ ;; (write-file checkout port)
+ ;; (force-output port)
+ ;; (get-hash)))))
+ ))
(build-system texlive-build-system)
(arguments ,`(,'quote (#:tex-directory ,(string-join (list
component id) "/"))))
(home-page ,home-page)
This successfully produces a definition, albeit without the hash field.
So it seems that the procedure 'download-svn-to-store ' is the source
of the original error. Any ideas on how to fix?
Paul.
next reply other threads:[~2020-09-09 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 11:53 Paul Garlick [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-10 16:19 getting started with the texlive importer Paul Garlick
2020-09-10 17:02 ` John Soo
2020-09-10 18:20 ` Ricardo Wurmus
2020-09-14 13:52 ` Paul Garlick
2020-09-08 9:15 Paul Garlick
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=04eeb383787339369224b9a8ad5e568eaa5cc6e6.camel@tourbillion-technology.com \
--to=pgarlick@tourbillion-technology.com \
--cc=guix-devel@gnu.org \
/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).