From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: How to install OBS plugins and scripts?
Date: Thu, 25 Aug 2022 20:08:20 +0000 [thread overview]
Message-ID: <LU7gWu2O43ME6euKRsv8vUI1Jj30tfR3S9TOP2eQwyQIcwKzHVUvbXZCgn55ekXiuJBwD5wazuqmk7SkGSyq7fITFrAwH1yjYyhd8JUFmvA=@elenq.tech> (raw)
In-Reply-To: <87ilmpo7in.fsf@pelzflorian.de>
Hi,
------- Original Message -------
On Thursday, August 18th, 2022 at 6:12 PM, pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> wrote:
> Ekaitz Zarraga ekaitz@elenq.tech writes:
>
> > Does anyone have OBS plugins?
>
>
> Not me, but maybe it helps that Andrew Tropin wrote in
> https://lists.gnu.org/archive/html/guix-patches/2021-01/msg01022.html
>
> that you can use OBS_PLUGINS_DATA_PATH and OBS_PLUGINS_PATH and made obs
> plugins that are shipped with guix use those.
>
> > Also our OBS does not depend on Python or Lua so I don't think it's
> > able to run scripts... Anyone has info about this?
>
>
> I suppose Python or Lua just need to be installed along with obs?
>
> Sorry I did not try any of this.
>
> Regards,
> Florian
Thanks a lot for your answer Florian.
I wanted to dig on this further in order to answer you but I didn't have the time to do my proper research.
I just want to thank you for your help. I'll dig on this further and answer back if I find any solution.
I'll contact Andrew directly too.
Thanks again,
Ekaitz
next prev parent reply other threads:[~2022-08-25 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 15:07 How to install OBS plugins and scripts? Ekaitz Zarraga
2022-08-18 16:12 ` pelzflorian (Florian Pelz)
2022-08-25 20:08 ` Ekaitz Zarraga [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-26 5:48 Andrew Tropin
2022-08-26 11:47 ` 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='LU7gWu2O43ME6euKRsv8vUI1Jj30tfR3S9TOP2eQwyQIcwKzHVUvbXZCgn55ekXiuJBwD5wazuqmk7SkGSyq7fITFrAwH1yjYyhd8JUFmvA=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=help-guix@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.