unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: 24737@debbugs.gnu.org
Subject: bug#24737: `guix lint` should not check patch-file-names on inherited sources
Date: Wed, 19 Oct 2016 21:51:32 +0200	[thread overview]
Message-ID: <87eg3c5d8b.fsf@gnu.org> (raw)
In-Reply-To: <87zim05tvp.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> (Marius Bakke's message of "Wed, 19 Oct 2016 14:51:54 +0100")

Marius Bakke <mbakke@fastmail.com> skribis:

> After patching 'notmuch', `guix lint -c patch-file-names` does not pass
> for 'python-notmuch' which inherits the source from 'notmuch'.

I agree but that’s not quite possible: the “inheritance” relation (which
is really just a copy of a record) is not known at run time.

So we’d need another trick to guess whether a patch is coming from
elsewhere and should consequently be ignored by ‘lint’.

Thanks,
Ludo’.

  reply	other threads:[~2016-10-19 19:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 13:51 bug#24737: `guix lint` should not check patch-file-names on inherited sources Marius Bakke
2016-10-19 19:51 ` Ludovic Courtès [this message]
2016-10-22 18:53   ` Marius Bakke
2016-10-22 19:07     ` Marius Bakke
2016-10-24 20:03       ` Ludovic Courtès

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=87eg3c5d8b.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=24737@debbugs.gnu.org \
    --cc=mbakke@fastmail.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).