From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jack Hill <jackhill@jackhill.us>
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>, 52730@debbugs.gnu.org
Subject: [bug#52730] [PATCH] gnu: gst-plugins/selection: Make #:configure-flags optional.
Date: Mon, 22 Jan 2024 11:36:56 -0500 [thread overview]
Message-ID: <87mssx2ul3.fsf@gmail.com> (raw)
In-Reply-To: <3da5b151a9e9312953660549fbbf5fa9153ac275.camel@gmail.com> (Liliana Marie Prikler's message of "Tue, 16 Aug 2022 21:46:31 +0200")
Hello Jack,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Hi Jack,
>
> Am Freitag, dem 24.12.2021 um 00:17 -0500 schrieb Jack Hill:
>> On Fri, 24 Dec 2021, Liliana Marie Prikler wrote:
>>
>> > Hi,
>> >
>> > Am Dienstag, dem 21.12.2021 um 22:34 -0500 schrieb Jack Hill:
>> > > * gnu/packages/gstreamer.scm (gst-plugins/selection): Provide the
>> > > empyt list as a default value for #:configure-flags.
>>
>> > The current implementation ought to copy pre-existing configure-
>> > flags
>> > as-is if you don't supply flags on your own. I personally believe
>> > that's preferable over an empty value, that will probably be reset.
>> > WDYT?
>>
>> Yes, I agree that the current implementation ought to, but it
>> doesn't.
>> Instead it complains:
>>
>> """
>> ice-9/psyntax.scm:2794:12: In procedure syntax-violation:
>> Syntax error:
>> unknown location: quote: bad syntax in form quote
>> """
> Is this still an issue? Also try staging, which has gstreamer 1.20 and
> some gexp-improvements for gst-plugins/selection.
Ping :-)
--
Thanks,
Maxim
prev parent reply other threads:[~2024-01-22 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 3:34 [bug#52730] [PATCH] gnu: gst-plugins/selection: Make #:configure-flags optional Jack Hill
2021-12-24 0:44 ` Liliana Marie Prikler
2021-12-24 5:17 ` Jack Hill
2021-12-24 6:37 ` Jack Hill
2021-12-24 7:56 ` Liliana Marie Prikler
2022-08-16 19:46 ` Liliana Marie Prikler
2024-01-22 16:36 ` Maxim Cournoyer [this message]
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=87mssx2ul3.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=52730@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
--cc=liliana.prikler@gmail.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).