[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] doc: Update contribution guidelines on patches, etc.
From: |
Maxime Devos |
Subject: |
Re: [PATCH] doc: Update contribution guidelines on patches, etc. |
Date: |
Tue, 9 Aug 2022 18:45:56 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 |
On 06-08-2022 08:55, Liliana Marie Prikler wrote:
+If your package has a bug that takes multiple lines to fix,
I don't think this is true for replacing all instances of "foo" by
"/gnu/store/.../bin/foo" in a file.
or a fix
+has already been accepted upstream, patches are the preferred way of
+eliminating said bug
+Refer to the @code{origin} record documentation
+(particularly the fields @code{snippet} and @code{modules}), for more
+information (@pxref{origin Reference}).
+
The "Refer to the ... documentation for more information" occurred in
the old version of (guix)Snippets versus Phases. However, back then, I
did not find more information on how to decide between snippets, patches
and phases, and neither do I now.
Maybe:
+Refer to the @code{origin} record documentation
+(@pxref{origin Reference}) (particularly the fields @code{snippet} and
@code{modules})
+for more information on how to use snippets
, to avoid a reader's assumption that that section contains information
on deciding between snippets, phases and patches.
+ Furthermore, as with patches, modifying the snippets causes two derivations
to be built.
This is true, but I don't think reviewers and package authors have to
worry about that.
Such changes include, but are not limited to fixes of the
+build script(s) or embeddings of store paths (e.g. replacement of
+@file{/bin/sh} with @code{(search-input-file inputs "bin/sh")}).
Include what? I think you need to close the subsentence here:
+Such changes include, but are not limited to, fixes of the build
+script(s) or embeddings of store paths (e.g. [...])
[...]
+Build phases are limited in that they do not modify the source
+derivation. Thus, they are inadequate for changes that are to be
+reflected in the source code. On the other hand, they only cause a
+single rebuild and are thus slightly easier to debug than phases and
+snippets.
Derivations are a rather low-level concept, could they be avoided in the
origin and phases documentation?
+Build phases are limited in that they do not modify the source
+derivation. Thus, they are inadequate for changes that are to be
+reflected in the source code. On the other hand, they only cause a
+single rebuild and are thus slightly easier to debug than phases and
+snippets.
See Andreas' comment on phase->snippet.
Also, do I understand correctly that the argument here is that 'single
rebuild -> less compilation time -> easier to debug'?
Greetings,
Maxime.
OpenPGP_0x49E3EE22191725EE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
- v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches., Maxime Devos, 2022/08/05
- Message not available
- Re: v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches., blake, 2022/08/05
- Re: v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches., Maxime Devos, 2022/08/09
- Re: v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches., blake, 2022/08/10
- Re: v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches., Maxime Devos, 2022/08/10
- Re: v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches., blake, 2022/08/10
- Re: v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches., Maxime Devos, 2022/08/10
[PATCH] doc: Update contribution guidelines on patches, etc., Liliana Marie Prikler, 2022/08/06
- Re: [PATCH] doc: Update contribution guidelines on patches, etc.,
Maxime Devos <=
- Re: [PATCH] doc: Update contribution guidelines on patches, etc., Liliana Marie Prikler, 2022/08/09
- Re: [PATCH] doc: Update contribution guidelines on patches, etc., Maxime Devos, 2022/08/09
- Re: [PATCH] doc: Update contribution guidelines on patches, etc., Liliana Marie Prikler, 2022/08/09
- Re: [PATCH] doc: Update contribution guidelines on patches, etc., Maxime Devos, 2022/08/09
- Re: [PATCH] doc: Update contribution guidelines on patches, etc., Liliana Marie Prikler, 2022/08/10
- Re: [PATCH] doc: Update contribution guidelines on patches, etc., Maxime Devos, 2022/08/09
[PATCH v2] doc: Update contribution guidelines on patches, etc., Liliana Marie Prikler, 2022/08/10
Re: v2: A proposal of a consistent set of clear rules and guidelines involving snippets, phases and patches., Andreas Enge, 2022/08/08