From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: malte.f.gerdes@gmail.com, 43906@debbugs.gnu.org
Subject: [bug#43906] [PATCH] Add missing dependencies of Slic3r
Date: Sat, 10 Oct 2020 22:26:59 +0200 [thread overview]
Message-ID: <874kn1zv1o.fsf@nckx> (raw)
In-Reply-To: <20201010195303.GA27775@jurong>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Andreas,
Andreas Enge 写道:
> Then this:
> starting phase `check'
> t/01_load.t .......... ok
> t/zy_pod_coverage.t .. skipped: Test::Pod::Coverage 1.00
> required for testing POD coverage
> t/zz_pod.t ........... skipped: Test::Pod 1.00 required for
> testing POD
>
> Similarly, add (native-)inputs?
I deliberately ignore these when I see them.
Like test coverage or code formatting tests, these test the source
code (here: documentation) itself, not the build result. IMO
that's useful for upstream authors but not for us redistributors.
> Concerning normal vs. propagated inputs, I must confess my
> ignorance of perl; do all perl packages need to be propagated?
Yes, unless a PERL5LIB wrapper is used instead. Binaries &
scripts can be wrapped, Perl modules can't.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-10 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 13:52 [bug#43906] [PATCH] Add missing dependencies of Slic3r Malte Frank Gerdes
2020-10-10 19:53 ` Andreas Enge
2020-10-10 20:26 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-10-13 19:27 ` [bug#43906] [PATCH v2] perl-alien-wxwidgets Malte Frank Gerdes
2023-02-09 20:47 ` [bug#43906] [PATCH v3] perl-wx Andreas Enge
2023-02-18 11:05 ` bug#43906: " Andreas Enge
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=874kn1zv1o.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=43906@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=malte.f.gerdes@gmail.com \
--cc=me@tobias.gr \
/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).