Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] External Library Dependencies and Testability
Date: Sat, 27 Aug 2022 13:19:42 +0200
Message-ID: <CAPYw7P4x=yUmTgp15RSPhAh0BHXaL521PiJ86-_3EHjec3Ayng@mail.gmail.com> (raw)
In-Reply-To: <DM8P223MB03656169CACE6519E65211A4BA749@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On Sat, Aug 27, 2022 at 11:30 AM Soft Works <softworkz@hotmail.com> wrote:

> Hi,
>
> I don’t want to get involved in the ipfsgateway discussion, but the part
> about
> external library version dependencies and testability reminded me of some
> recent thoughts: I wonder whether it wouldn’t make sense to maintain a
> version
> reference for external libraries in a way that at any point in (repo) time
> there’s a clearly defined set of dependency library versions.
> This could provide a number of benefits, like:
>
> - enable testability where external libs are involved
> - improve reproducibility of issues with external libs
> - serve as an orientation for library versions to use
>   for static builds
> - possibly more
>
> It could still be purely informational but provide a defined reference
> point for dependency library versions whenever needed or useful.
>
> The configure script could get an option like 'strict_references' option
> would cause it to error out when it doesn't find the exact versions of
> libs.
>
> Another use case for this would be for ensuring reproducibility of
> (static) builds.


Its all nice, but there is severe lack of resources to do testing.


>
>
> softworkz
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      reply	other threads:[~2022-08-27 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27  9:30 Soft Works
2022-08-27 11:19 ` Paul B Mahol [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPYw7P4x=yUmTgp15RSPhAh0BHXaL521PiJ86-_3EHjec3Ayng@mail.gmail.com' \
    --to=onemda@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git