all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Andrew Tropin <andrew@trop.in>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to install OBS plugins and scripts?
Date: Fri, 26 Aug 2022 11:47:14 +0000	[thread overview]
Message-ID: <CxC1i7-37BJhwWGCZ9HXbFUd_hJ2ruGkFOrnZwG4Gh-p0JNSG61picN26HRixYcKL1nIEZ9_7wIhcSbBEMC1SMKc-l0UmvZYeUTqMCgF7IU=@elenq.tech> (raw)
In-Reply-To: <87wnava739.fsf@trop.in>

Thanks a lot Andrew!

Just tested the scripts and they work well.

Also, mention that you can keep them anywhere you want, which is also a plus.

------- Original Message -------
On Friday, August 26th, 2022 at 7:48 AM, Andrew Tropin <andrew@trop.in> wrote:


> OBS native plugins should install their .so files to lib/obs-plugins/
> and data files to share/obs/obs-plugins/ and they will be automatically
> loaded, when obs installed in the same profile (directories for finding
> plugins defined in native-search-paths of obs package). Also, take a
> look at obs-* packages for examples on how to package plugins.
> 
> There was no scripts support, updated obs package to 27.2.4 and enabled
> python and lua scripting support.
> 
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=4ff0ceb26462d27281eed5cf789ca4158f94409a
> 
> --
> Best regards,
> Andrew Tropin


  reply	other threads:[~2022-08-26 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  5:48 How to install OBS plugins and scripts? Andrew Tropin
2022-08-26 11:47 ` Ekaitz Zarraga [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-18 15:07 Ekaitz Zarraga
2022-08-18 16:12 ` pelzflorian (Florian Pelz)
2022-08-25 20:08   ` Ekaitz Zarraga

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='CxC1i7-37BJhwWGCZ9HXbFUd_hJ2ruGkFOrnZwG4Gh-p0JNSG61picN26HRixYcKL1nIEZ9_7wIhcSbBEMC1SMKc-l0UmvZYeUTqMCgF7IU=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=andrew@trop.in \
    --cc=help-guix@gnu.org \
    /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.