From: "Diederick C. Niehorster" <dcnieho@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC v2] avdevice: lock to minor version of avformat
Date: Thu, 3 Mar 2022 10:03:55 +0100
Message-ID: <CABcAi1jixJcJOmXXxG7YMiTDfhCLi-O6woP7FxRgH3Oe=F9Siw@mail.gmail.com> (raw)
In-Reply-To: <CABcAi1jWM6ZHKhRfOKQBqjPKLXLmBX3F_we7ef+TafnV_8egYQ@mail.gmail.com>
Hi Andreas,
On Mon, Jan 3, 2022 at 12:03 PM Diederick C. Niehorster <dcnieho@gmail.com>
wrote:
> Hi Andreas,
>
> Thanks for the comments!
>
> On Mon, Jan 3, 2022 at 11:02 AM Andreas Rheinhardt
> <andreas.rheinhardt@outlook.com> wrote:
> >
> > Diederick Niehorster:
> > > As per discussion on the list (
> > > https://ffmpeg.org/pipermail/ffmpeg-devel/2021-June/281513.html, see
> > > especially
> https://ffmpeg.org/pipermail/ffmpeg-devel/2021-June/281586.html),
> > > to resolve the the unholy ABI-relationship between libavdevice and
> > > libavformat and allow easier working on the part of the avdevice API
> > > that lives in avformat, lock avdevice to a specific major and minor
> > > version of avformat.
> > >
> > > Signed-off-by: Diederick Niehorster <dcnieho@gmail.com>
> > > ---
> >
> > 1. If this patch intends to make it illegal to use libavdevice together
> > with libavformat with a different minor version than it was compiled
> > against, then the most basic requirement of this is to actually properly
> > document it and not add stuff that might cause linking failure if used
> > in a way that runs afoul of your undocumented new requirements.
>
> Absolutely, documentation is required. Should that be in (amongst
> local to the function in the header)?
>
I want to prepare a next version to get this discussion going. Where should
i document that it is illegal to use libavdevice together with libavformat
with a different minor version?
The versioning documentation starting on line 47 in /libavutil/avutil.h?
All the best,
Dee
_______________________________________________
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".
next prev parent reply other threads:[~2022-03-03 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 15:07 Diederick Niehorster
2022-01-03 10:02 ` Andreas Rheinhardt
2022-01-03 11:03 ` Diederick C. Niehorster
2022-03-03 9:03 ` Diederick C. Niehorster [this message]
2022-03-03 14:38 ` Andreas Rheinhardt
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='CABcAi1jixJcJOmXXxG7YMiTDfhCLi-O6woP7FxRgH3Oe=F9Siw@mail.gmail.com' \
--to=dcnieho@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