all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: "Ellis Kenyő" <me@elken.dev>
Cc: 46215@debbugs.gnu.org
Subject: [bug#46215] [PATCH] Add yadm
Date: Sun, 31 Jan 2021 21:36:52 +0100	[thread overview]
Message-ID: <0ff6a0c2cc9a2f65cd51c1eeb9e6a33aa4789766.camel@student.tugraz.at> (raw)
In-Reply-To: <87czxkc0yv.fsf@elken.dev>

Hi Ellen,

Am Sonntag, den 31.01.2021, 20:16 +0000 schrieb Ellis Kenyő:
> Hi Leo,
> 
> Thanks for the feedback.
> 
> > Your commit is missing a ChangeLog in its message.
> This will be added with the next patch.
> 
> > Document why (i.e. "no check target").
> I have also added similar comments for the other removed stages.
That's not as important, gnu-build-system is often used as base for
packages and build system, that don't actually have configure.  For
disabled tests, however, it is not clear without comment whether they
fail or whether they simply don't exist.

> > yadm has a few things you need to patch.  For one, its shebang 
> > is
> > /bin/sh despite requiring bash.  Also it contains a large number 
> > of
> > _PROGRAM variables, which would be need to be replaced by their 
> > actual
> > store path (use the which procedure for that).
> 
> Patch them to be the $(which <exe>) expression or evaluate that?
> If the latter, I'm not sure how that would handle installing deps
> retroactively.
You'd add the packages, that define those programs as inputs, then
you do something along the lines of

  (substitute* "yadm" 
    (("(.*)_PROGRAM=\"(.*)\"" all var prog)
     (format #f "~a_PROGRAM=~s" var (which prog))))

inside some phase after unpack.
Please apologize if the snippet above doesn't actually work for your
case, I haven't tried it.

By the way, git format-patch seems to swallow the Umlaut (or however
it's called in your language) in your surname.  If you want it to be
that way, then fair enough, just know that there's no policy
prohibiting UTF-8 in committer names.

Regards,
Leo





  reply	other threads:[~2021-01-31 20:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 16:47 [bug#46215] [PATCH] Add yadm guix-patches--- via
2021-01-31 17:38 ` Leo Prikler
2021-01-31 20:16   ` guix-patches--- via
2021-01-31 20:36     ` Leo Prikler [this message]
2021-02-01  3:44       ` guix-patches--- via
2021-02-01  8:13         ` Leo Prikler
2021-02-01 10:06           ` guix-patches--- via
2021-02-01 11:44             ` Leo Prikler
2021-02-06 10:05               ` Ellis Kenyő via Guix-patches via
2021-02-06 10:48                 ` Leo Prikler
2021-02-06 10:58                   ` Ellis Kenyő via Guix-patches via
2021-02-06 11:22                     ` Leo Prikler
2021-02-06 11:26                       ` Ellis Kenyő via Guix-patches via
2021-02-06 11:46                       ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-06 12:41                         ` Leo Prikler
2021-02-06 11:30                     ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-06 11:43                       ` Ellis Kenyő via Guix-patches via
2021-02-06 11:58                       ` Leo Prikler
2021-02-06 12:03                         ` Tobias Geerinckx-Rice via Guix-patches via
2022-09-09  0:01 ` [bug#46215] [PATCH] gnu: " kiasoc5 via Guix-patches via

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=0ff6a0c2cc9a2f65cd51c1eeb9e6a33aa4789766.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=46215@debbugs.gnu.org \
    --cc=me@elken.dev \
    /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.