From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Leo Famulari <leo@famulari.name>
Cc: 44806@debbugs.gnu.org
Subject: [bug#44806] [PATCH staging 5/6] gnu: Add pitivi.
Date: Tue, 15 Dec 2020 08:55:17 +0100 [thread overview]
Message-ID: <5ec8e559cc35936d03bfbc88593a36d09a61649c.camel@student.tugraz.at> (raw)
In-Reply-To: <X9hk346ZFj2Sk8oX@jasmine.lan>
Am Dienstag, den 15.12.2020, 02:25 -0500 schrieb Leo Famulari:
> On Sun, Nov 22, 2020 at 09:36:24PM +0100, Leo Prikler wrote:
> > * gnu/packages/video.scm (pitivi): New variable.
>
> Overall LGTM.
>
> > + ("gst-plugins-bad"
> > + ,(gst-plugins/selection gst-plugins-bad
> > + #:plugins '("debugutils"
> > "transcoder")
> > + #:configure-flags '("-
> > Dintrospection=enabled")))
> > + ;; We've only added inputs for what Pitivi deems
> > either
> > + ;; necessary or optional. Let the user's
> > packages take
> > + ;; precedence in case they have e.g. the full
> > gst-plugins-bad.
> > + `("GST_PLUGIN_SYSTEM_PATH" suffix
> > + (,(getenv "GST_PLUGIN_SYSTEM_PATH")))))
>
> Do we do this to save space? Or to avoid the rest of the bad plugins?
Both would be valid reasons to do this imo. Adding more bad plugins is
likely also not going to increase the number of features Pitivi offers.
next prev parent reply other threads:[~2020-12-15 7:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 20:34 [bug#44806] [PATCH staging 0/6] Add Pitivi Leo Prikler
2020-11-22 20:36 ` [bug#44806] [PATCH staging 1/6] gnu: libpeas: Update to 1.28.0 Leo Prikler
2020-11-22 20:36 ` [bug#44806] [PATCH staging 2/6] gnu: gst-editing-services: Build with introspection Leo Prikler
2020-12-15 7:17 ` Leo Famulari
2020-11-22 20:36 ` [bug#44806] [PATCH staging 3/6] gnu: Add gst-plugins/selection Leo Prikler
2020-12-15 7:19 ` Leo Famulari
2020-11-22 20:36 ` [bug#44806] [PATCH staging 4/6] gnu: Update and deprecate gst-transcoder Leo Prikler
2020-12-15 7:21 ` Leo Famulari
2020-12-15 8:45 ` Leo Prikler
2020-12-15 21:21 ` Leo Famulari
2020-11-22 20:36 ` [bug#44806] [PATCH staging 5/6] gnu: Add pitivi Leo Prikler
2020-12-15 7:25 ` Leo Famulari
2020-12-15 7:55 ` Leo Prikler [this message]
2020-12-15 21:31 ` Leo Famulari
2020-12-16 0:18 ` Leo Prikler
2020-12-29 18:28 ` Leo Prikler
2020-12-29 19:04 ` Leo Famulari
2020-12-29 19:27 ` bug#44806: " Leo Prikler
2020-11-22 20:36 ` [bug#44806] [PATCH staging 6/6] gnu: ffmpeg-4.2: Remove rav1e from inputs Leo Prikler
2020-12-15 8:04 ` Leo Famulari
2020-12-15 7:16 ` [bug#44806] [PATCH staging 0/6] Add Pitivi Leo Famulari
2020-12-15 9:05 ` Leo Prikler
2020-12-15 9:03 ` [bug#44806] [PATCH v2 1/5] gnu: libpeas: Update to 1.28.0 Leo Prikler
2020-12-15 9:03 ` [bug#44806] [PATCH v2 2/5] gnu: gst-editing-services: Build with introspection Leo Prikler
2020-12-15 9:03 ` [bug#44806] [PATCH v2 3/5] gnu: Add gst-plugins/selection Leo Prikler
2020-12-15 9:03 ` [bug#44806] [PATCH v2 4/5] gnu: Update and deprecate gst-transcoder Leo Prikler
2020-12-15 9:03 ` [bug#44806] [PATCH v2 5/5] gnu: Add pitivi Leo Prikler
2020-12-15 21:20 ` Leo Famulari
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=5ec8e559cc35936d03bfbc88593a36d09a61649c.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=44806@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).