all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 01/26] gnu: Add perl-file-pushd.
Date: Fri, 24 Mar 2017 14:32:59 +0100	[thread overview]
Message-ID: <87inmy4x6c.fsf@gmail.com> (raw)
In-Reply-To: <af5a308d-ca1f-9507-328b-5109f8cddff1@uq.edu.au>

Hi Ben,

Ben Woodcroft writes:

> Hi,
>
>
> On 24/03/17 18:13, Alex Sassmannshausen wrote:
>> Hi Kei,
>>
>> Kei Kebreau writes:
>>
>>> This series of packages builds and lints fine for me. There are over 200
>>> dependent packages that would have to be rebuilt though, and
>>> core-updates is frozen to my knowledge. We can save this for the next
>>> core-updates cycle, though!
>>>
>>> Other Guix users, please correct me if I'm wrong.
> According to the established guidelines, this should be OK for master
> since it affects <300 packages, so if all dependent packages build then
> I don't see why we shouldn't do that.
>
> https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html

Cheers for your comments, very enlightening!  I'm afraid I'm out of my
depth making this decision here.  I'm happy to let my computer rebuild
those 200 packages to see whether the dependent packages build — but
I'm not sure how I would go about testing that.  See below for a theory…?

>> Thanks for the review!
>>
>> What command do you use to check the number of packages that would have
>> to be rebuilt?  I'm asking, because if they are mainly perl libraries
>> then that figure of 200 really isn't that big of a deal: most perl libs
>> build super fast.
> To check the number of packages use "guix refresh -l"

Interesting… so to establish the packages to be rebuilt as a result of
my patch series, would that be:

guix refresh -l perl-scalar-list-utils perl-parse-cpan-meta      \
perl-cpan-meta-requirements perl-yaml perl-variable-magic        \
perl-time-duration-parse perl-test-warnings perl-test-simple     \
perl-test-exception perl-test-cleannamespaces perl-sub-name      \
perl-params-validate perl-package-deprecationmanager perl-moose  \
perl-module-runtime-conflicts perl-devel-partialdump             \
perl-devel-overloadinfo perl-cpan-meta-check perl-common-sense   \
perl-clone perl-class-load perl-capture-tiny perl-b-hooks-endofscope

Building the following 24 packages would ensure 248 dependent packages
are rebuilt: edirect-4.10 perl-modern-perl-1.20150127
perl-text-neattemplate-0.1101 perl-encode-detect-1.01
perl-list-someutils-0.52 perl-db-file-1.838 pam-krb5-4.7
perl-test-trailingspace-0.0300 sslh-1.18 perl-mail-spf-v2.9.0
gerbv-2.6.1 netsurf-3.6 perl-config-ini-0.025 perl-anyevent-i3-0.16
tophat-2.1.0 perl-test-class-most-0.08 gnucash-2.6.15 surfraw-2.2.9
biber-2.5 biber-next-2.6 stow-2.2.2 perl-x11-xcb-0.16 roary-3.7.0
hydra-20151030.1ff48da

Does this mean, that in order to test this I would now simply try to
rebuild the 24 listed packages?

Cheers,

Alex

  reply	other threads:[~2017-03-24 13:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 14:00 [PATCH 01/26] gnu: Add perl-file-pushd Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 02/26] gnu: Add perl-test-needs Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 03/26] gnu: perl-b-hooks-endofscope: Update to 0.21 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 04/26] gnu: perl-capture-tiny: Update to 0.46 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 05/26] gnu: perl-class-load: Update to 0.23 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 06/26] gnu: perl-clone: Update to 0.38 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 07/26] gnu: perl-common-sense: Update to 3.74 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 08/26] gnu: perl-cpan-meta-check: Update to 0.011 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 09/26] gnu: perl-devel-overloadinfo: Update to 0.004 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 10/26] gnu: perl-devel-partialdump: Update to 0.18 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 11/26] gnu: perl-module-runtime-conflicts: Update to 0.003 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 12/26] gnu: perl-moose: Update to 2.2004 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 13/26] gnu: perl-package-deprecationmanager: Update to 0.17 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 14/26] gnu: perl-params-validate: Update to 1.26 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 15/26] gnu: perl-sub-name: Update to 0.21 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 16/26] gnu: perl-test-cleannamespaces: Update to 0.22 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 17/26] gnu: perl-test-exception: Update to 0.43 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 18/26] gnu: perl-test-simple: Update to 1.302078 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 19/26] gnu: perl-test-warnings: Update to 0.026 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 20/26] gnu: perl-time-duration-parse: Update to 0.13 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 21/26] gnu: perl-variable-magic: Update to 0.61 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 22/26] gnu: perl-yaml: Update to 1.23 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 23/26] gnu: perl-cpan-meta-requirements: Update to 2.140 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 24/26] gnu: perl-cpan-meta-yaml: Update to 0.018 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 25/26] gnu: perl-parse-cpan-meta: Update to 2.150010 Alex Sassmannshausen
2017-03-23 14:00 ` [PATCH 26/26] gnu: perl-scalar-list-utils: Update to 1.47 Alex Sassmannshausen
2017-03-24  3:18 ` [PATCH 01/26] gnu: Add perl-file-pushd Kei Kebreau
2017-03-24  8:13   ` Alex Sassmannshausen
2017-03-24 12:51     ` Ben Woodcroft
2017-03-24 13:32       ` Alex Sassmannshausen [this message]
2017-03-24 14:26         ` Kei Kebreau
2017-03-25 16:53           ` Alex Sassmannshausen
2017-03-24 14:44         ` Tobias Geerinckx-Rice

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87inmy4x6c.fsf@gmail.com \
    --to=alex.sassmannshausen@gmail.com \
    --cc=b.woodcroft@uq.edu.au \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.