From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [PATCH] doc: Run guix refresh -l to find out about dependent
	packages.
Date: Thu, 28 Jul 2016 15:09:51 +0200
Message-ID: <87shuthpsw.fsf@gnu.org>
References: <87twfaggmx.fsf@we.make.ritual.n0.is>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47175)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bSl4a-0006DK-31
	for guix-devel@gnu.org; Thu, 28 Jul 2016 09:10:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bSl4U-0003wF-6D
	for guix-devel@gnu.org; Thu, 28 Jul 2016 09:09:58 -0400
In-Reply-To: <87twfaggmx.fsf@we.make.ritual.n0.is> (ng0@we.make.ritual.n0.is's
	message of "Thu, 28 Jul 2016 11:13:10 +0000")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org

ng0 <ng0@we.make.ritual.n0.is> skribis:

> --- a/doc/contributing.texi
> +++ b/doc/contributing.texi
> @@ -328,6 +328,21 @@ extensions---or to the operating system kernel---e.g=
., reliance on
>  @code{uname} or @file{/proc} files.
>=20=20
>  @item
> +Run @command{guix refresh --list-dependent} (@pxref{Invoking guix refres=
h})
> +to find out how many packages would rebuild based on your patch.
> +When your patch touches important or a big number of packages, it is
> +prefered to be applied on the git branch core-updates or core-updates-ne=
xt.
> +
> +@example
> +guix refresh -l libgcrypt
> +Building the following 822 packages would ensure 2221 dependent packages
> +are rebuilt:
> +@end example
> +
> +This is a good example for a number which indicates that a change to
> +libgcrypt would not simply be applied on master.

=E2=80=98guix refresh -l=E2=80=99 is already mentioned in that section:

  https://www.gnu.org/software/guix/manual/html_node/Submitting-Patches.html

The specific branch names are not mentioned, but that=E2=80=99s also because
this process is still in flux.  =E2=80=9Ccore-updates=E2=80=9D initially me=
ant =E2=80=9Cupdates
to the core=E2=80=9D, where =E2=80=9Ccore=E2=80=9D designates GCC, libc, Bi=
nutils, and a few
other packages that make up the implicit inputs of gnu-build-system.

Python, libgcrypt, and similar packages are not =E2=80=9Ccore=E2=80=9D pack=
ages,
strictly speaking.  Ideally, we=E2=80=99d run =E2=80=98python-updates=E2=80=
=99,
=E2=80=98libgcrypt-updates=E2=80=99, etc. branches, but whether we do this =
depends on
our build farm capacity and on its current load.

In short, I think it=E2=80=99s best not too give too many details about a
process that=E2=80=99s not set in stone.  :-)

Thoughts?

Ludo=E2=80=99.