From: ng0 <contact.ng0@cryptolab.net>
To: Thomas Sigurdsen <thomas.sigurdsen@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Package Definitions and Maintenance
Date: Sun, 2 Apr 2017 10:56:13 +0000 [thread overview]
Message-ID: <20170402105613.qy4bqfcsm6g6gnfo@abyayala> (raw)
In-Reply-To: <20170402114445.33e505b3@hitpoints>
Hi Thomas,
Thomas Sigurdsen transcribed 3.0K bytes:
> Hi Guix!
>
> I'm sending two threads with the same intro, read below the line for the
> questions.
>
> I've been playing around with guixsd on my day-to-day work laptop for a month
> or so now and have to say I'm thoroughly happy about how everything is put
> together and mostly _just works_.
>
> I'll note that I'm still very much learning guile and scheme. But the manual
> (https://www.gnu.org/software/guile/manual/) is amazing.
>
> -------------------------------------------------------------------------------------------------
>
> I have tried writing some package definitions
> (https://notabug.org/thomassgn/guixsd-configuration/src/master/modules/tms/).
> But I can not get it to even pass evaluation and I don't understand what is
> meant by 'procedure #f'. Assuming I somewhere have a value that should eval
> to a procedure but evals to false instead - I just don't understand where.
>
> The first warning about freetype I don't understand how to get around
> also. I've attached my output from running 'guix package -i wkhtmltopdf' at
> the end.
>
> I'm also curious: I'm happy to contribute the package definitions I write to
> guix; but I don't think I'm a reliable maintainer. That is, I don't know if I
> will have the capacity to update the definitions as upstream changes with time
> (I'm not reliable like that). Should I still send patches with package
> definitions?
Yes, we do not enforce a person per package becomes the maintainer
policy. The packages are collectively maintained, and while there are
people who pick groups of packages for various reasons they look after,
everyone has the freedom to update and care for the packages.
> My entire configuration with homemade modules can be found at:
> https://notabug.org/thomassgn/guixsd-configuration
>
>
> WARNING: (wkhtmltopdf): `freetype' imported from both (guix licenses) and
> (gnu packages fontutils) Backtrace:
> In ice-9/boot-9.scm:
> 4056: 19 [#<procedure 1148900 at ice-9/boot-9.scm:4051:3 ()>]
> 1727: 18 [%start-stack load-stack ...]
> 1732: 17 [#<procedure 115cb10 ()>]
> In unknown file:
> ?: 16 [primitive-load
> "/gnu/store/0icg6mr0cw74srvp39hms8fvh3s821yf-guix-0.12.0-7.aabe/bin/.guix-real"]
> In guix/ui.scm: 1228: 15 [run-guix-command package "-i" "wkhtmltopdf"]
> In ice-9/boot-9.scm:
> 160: 14 [catch srfi-34 #<procedure 1b71c00 at guix/ui.scm:432:2 ()> ...]
> 160: 13 [catch system-error ...]
> In guix/scripts/package.scm:
> 896: 12 [#<procedure 1b71c20 at guix/scripts/package.scm:884:4 ()>]
> 863: 11 [process-actions #<build-daemon 256.97 1b722c0> (# # # # ...)]
> In guix/ui.scm:
> 729: 10 [show-manifest-transaction # # # ...]
> In srfi/srfi-1.scm:
> 598: 9 [map #<procedure 4bd45c0 at guix/ui.scm:653:9 (name version output
> item)> ...] In guix/ui.scm:
> 658: 8 [#<procedure 4bd45c0 at guix/ui.scm:653:9 (name version output item)>
> "wkhtmltopdf" ...] In guix/packages.scm:
> 1134: 7 [package-output # # "out" ...]
> 786: 6 [cache! #<weak-key-hash-table 1a3da00 339/443> # # ...]
> 1092: 5 [thunk]
> 1024: 4 [bag->derivation # # #]
> In srfi/srfi-1.scm:
> 573: 3 [map #<procedure 356a150 at guix/packages.scm:1026:30 (t-1331428)> #]
> In guix/packages.scm:
> 846: 2 [expand-input # # # ...]
> In guix/store.scm:
> 1176: 1 [#<procedure 1a404a0 at guix/store.scm:1175:26 (store . args)> #
> # ...] In unknown file:
> ?: 0 [#f # "x86_64-linux" #f]
>
> ERROR: In procedure #f:
> ERROR: Wrong type to apply: #f
>
>
next prev parent reply other threads:[~2017-04-02 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 9:44 Package Definitions and Maintenance Thomas Sigurdsen
2017-04-02 10:56 ` ng0 [this message]
2017-04-03 13:21 ` Ludovic Courtès
2017-04-03 13:42 ` Ludovic Courtès
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=20170402105613.qy4bqfcsm6g6gnfo@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=help-guix@gnu.org \
--cc=thomas.sigurdsen@gmail.com \
/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.
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).