unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: gnu: shepherd: patch, snippet or phase
Date: Sat, 05 Mar 2022 22:49:27 +0100	[thread overview]
Message-ID: <84e13ef7d437062df5cca51a12e6da54929e0176.camel@telenet.be> (raw)
In-Reply-To: <YiPSbdXBeim+5xfY@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 2921 bytes --]

(as implied per zimoun's previous mail (‘FWIW, it would be unfair for
the patch to have the discussion here’), moved to guix-devel)

Leo Famulari schreef op za 05-03-2022 om 16:13 [-0500]:
> On Thu, Mar 03, 2022 at 07:25:22AM +0100, Maxime Devos wrote:
> > Leo Famulari schreef op wo 02-03-2022 om 18:50 [-0500]:
> > > Origin snippets should only be used to remove nonfree things
> > > from the upstream source code. All other changes should use
> > > patch files or a build phase.
> > 
> > Why?  If it's a source code change and it fits an origin snippet,
> > why not an origin snippet?  Why would the source in Guix need to
> match
> > the source upstream?
> 
> `guix build --source` is a tool to provide freely licensed source
> code
> to be used for any purpose, including building on systems besides
> Guix.
> 
> Using the Guix tools, there is no way to access the upstream source
> code
> without applying the snippets. The reason for that is that the origin
> snippet mechanism was introduced specifically to remove non-free
> components without making it easy to reverse the transformation.

It might be introduced for removing non-free components, that doesn't
mean it cannot be used for more.  Also, I don't see the point of ease
of reversing here. It's trivial to reverse the transformation induced
by the snippet: just delete the snippet in a git checkout.

> Compare that to patch files, which are easily reversed,

Removing a patch file by removing it from the 'patches' field is easy,
as easy as removing a snippet.  I assume you meant the additional
condition ‘... using only CLI tools’?

In that case, you have to: (1) run "guix build --source ..." to compute
the patched source (and maybe unpack), then (2) somehow know there's a
patch to revert, (3) clone guix, (4) find the location of the patch in
the git repo, (5) figure out the invocation of 'patch' command, and
possibly (6) repack the depatched source.  

As such, reversing patch files seems rather difficult to me, it seems
much simpler to just delete the patch inside Guix, and then we might as
well have used a snippet originally.

>  and build
> phases, which do not apply to `guix build --source`.
> 
> So, we have to be careful when using snippets, to ensure that the
> result
> of `guix build --source` is useful on any system, not just Guix.
> 
> More info:
> https://guix.gnu.org/manual/en/html_node/Snippets-versus-Phases.html
> 
> Please let me know if these guidelines are still unclear.

I am aware of the guideline of keeping the source usable outside Guix
systems.  AFAICT, in this case, the snippet modifying
Makefile.am/Makefile.in keeps the source usable on non-Guix systems.
In fact, it makes the source _more_ usable, both on Guix and non-Guix,
by working-around a Guile 3.0.5 compiler bug.  So I don't see any
problems here.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

       reply	other threads:[~2022-03-05 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220301182848.26694-1-attila@lendvai.name>
     [not found] ` <20220301184517.13439-1-attila@lendvai.name>
     [not found]   ` <992c3326a10e0bb28491f8226ebbe84aa93ad9ca.camel@telenet.be>
     [not found]     ` <aJFlM3mC27rhgpJ7Mr5IN7Zyb84HRFfGSJinSMwiKWGxoY8t6gjmUatPyK2y_S8PNSqHgnTUbGJ3NDoiNHDnjN2rHVbi80WbUntglsXEO1s=@lendvai.name>
     [not found]       ` <CAJ3okZ1vah5XFy3BVoc=hv0Ke5GxT+3M3uYo2CTNRZyPHz-mAQ@mail.gmail.com>
     [not found]         ` <15fbca84-83ed-43cd-9bd4-e187ccadf4ec@www.fastmail.com>
     [not found]           ` <5d684728965ec36c604e9b77f650055269e8588e.camel@telenet.be>
     [not found]             ` <YiPSbdXBeim+5xfY@jasmine.lan>
2022-03-05 21:49               ` Maxime Devos [this message]
2022-04-29 14:36                 ` gnu: shepherd: patch, snippet or phase zimoun
2022-05-01  6:34                   ` Zhu Zihao

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=84e13ef7d437062df5cca51a12e6da54929e0176.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=zimon.toutoune@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.
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).