public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] gstreamer-meson.eclass: New eclass required for gstreamer-1.18.0+
Date: Wed, 17 Mar 2021 16:24:03 +0200	[thread overview]
Message-ID: <38d0f9b9d6ad4ebab36a7c6690e1e52d10a80745.camel@gentoo.org> (raw)
In-Reply-To: <YFHL9QenOyeRR9sZ@cloudsdale.the-delta.net.eu.org>

Ühel kenal päeval, K, 17.03.2021 kell 10:29, kirjutas Haelwenn
(lanodan) Monnier:
> > My main initial question on this version is:
> > How does it behave with helper libraries from the same tarball?
> 
> It has been in my overlay for a while (haven't included all the
> splitted plugins though).
> 
> ie. 
> https://hacktivis.me/git/overlay/file/media-plugins/gst-plugins-hls/gst-plugins-hls-1.18.4.ebuild.html
> 
> > Basically what gstreamer_system_link function solved in the
> > autotools
> > eclass.
> > E.g., if you build gst-plugins-libvisual, is it building gstreamer-
> > audio, gstreamer-video and gstreamer-pbutils as well again
> > (automatically due to generated ninja dependencies), or picks them
> > up
> > from gst-plugins-base?
> 
> I think this particular one isn't solved yet. Mainly because it
> doesn't
> seems to have caused me issues yet.

I think it would be building it again, and then link it against that
new build, instead of the system version that it'll actually use at
runtime. That sounds like a recipe for hard to track issues down the
line.
But maybe if it works out fine right now, it's worth ignoring it at
first, and solving it later on.

> 
> > * Don't make nls optional
> 
> What's the reason for this? It's the case with gstreamer::gentoo.

OK, I guess we could keep it too - maybe someone needs for very
embedded builds.



  reply	other threads:[~2021-03-17 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  1:49 [gentoo-dev] [PATCH] gstreamer-meson.eclass: New eclass required for gstreamer-1.18.0+ Haelwenn (lanodan) Monnier
2021-03-17  1:57 ` Sam James
2021-03-17  9:15   ` Mart Raudsepp
2021-03-17  9:29     ` Haelwenn (lanodan) Monnier
2021-03-17 14:24       ` Mart Raudsepp [this message]
2021-03-17 16:13 ` Alec Warner
2021-03-23 12:44 ` [gentoo-dev] [PATCH v2] " Haelwenn (lanodan) Monnier
2021-03-23 13:05   ` Michał Górny

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=38d0f9b9d6ad4ebab36a7c6690e1e52d10a80745.camel@gentoo.org \
    --to=leio@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox