unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Andrew Tropin <andrew@trop.in>
Cc: 46113@debbugs.gnu.org, 45960-done@debbugs.gnu.org
Subject: [bug#45960] [PATCH] gnu: Add obs-spectralizer.
Date: Wed, 03 Feb 2021 11:43:37 +0100	[thread overview]
Message-ID: <87r1lxbfdy.fsf@gnu.org> (raw)
In-Reply-To: <CABrWRW0oSU1TTECMks0RUd0GECr+yh14cc0NvsmpjB5qqzHPrQ@mail.gmail.com> (Andrew Tropin's message of "Tue, 2 Feb 2021 12:53:11 +0300")

Hi,

Andrew Tropin <andrew@trop.in> skribis:

> It won't load until obs updated to the commit with OBS_PLUGINS*_PATH
> variables support [fn:1], but as you said it's future-proof and already
> installs to the correct location.
>
> There is another very similar patch, which adds another obs plugin. You
> probably already aware of it, but here is a link:
> http://issues.guix.gnu.org/45961. Accidentally, it has empty propagated
> inputs and I'm not sure if it will apply to current master at all, but I
> can update it if it's needed.
>
>
> * Footnotes
>
> [fn:1] http://issues.guix.gnu.org/46113

Ah ha!  So on ‘master’, there’s the OBS_PLUGINS_DIRECTORY patch that you
provided earlier, which is why I wrote that the plugins should work.

Should we wait for the next OBS release instead of packaging an
arbitrary commit?

Ludo’.




  reply	other threads:[~2021-02-03 10:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 16:57 [bug#45960] [PATCH] gnu: Add obs-spectralizer Andrew Tropin
2021-02-02  9:34 ` bug#45960: " Ludovic Courtès
2021-02-02  9:53   ` [bug#45960] " Andrew Tropin
2021-02-03 10:43     ` Ludovic Courtès [this message]
2021-02-03 14:00       ` [bug#45960] [bug#46113] bug#45960: " 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

  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=87r1lxbfdy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=45960-done@debbugs.gnu.org \
    --cc=46113@debbugs.gnu.org \
    --cc=andrew@trop.in \
    /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).