Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [SDR][RFC] libavradio branch changes
Date: Mon, 3 Jul 2023 16:17:47 +0200
Message-ID: <20230703141747.GP1093384@pb2> (raw)
In-Reply-To: <CAPYw7P4RutV8Vxew2yD550fi9UntydstYAkVv8EJPg7Z6spWTg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4209 bytes --]

On Mon, Jul 03, 2023 at 10:54:05AM +0200, Paul B Mahol wrote:
> On Mon, Jul 3, 2023 at 7:48 AM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
> 
> > Hi
> >
> > the new libavradio in its new repository needs some changes the problem
> > is that maintaining it in a separate repository AND seperate directory is
> > not
> > so simple
> > But let me show this in numbers, this is the stats of the changes related
> > to the build
> > system that would need to be maintained:
> >
> > commit e262fd4b85a1a3ddf34c365bb88e54cdc6be53eb
> > Author: Michael Niedermayer <michael@niedermayer.cc>
> > Date:   Sun Jul 2 14:08:42 2023 +0200
> >
> >     Move sdr to new libavradio
> >
> >     Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> >
> >  Makefile                                          |   5 +--
> >  configure                                         |  36
> > ++++++++++++++++++++--
> >  fftools/ffmpeg.c                                  |   5 +++
> >  fftools/ffplay.c                                  |   4 +++
> >  fftools/ffprobe.c                                 |   4 +++
> >  fftools/opt_common.c                              |  62
> > ++++++++++++++++++++++++++++++++++---
> >  fftools/opt_common.h                              |  27 ++++++++++++++++
> >  libavdevice/Makefile                              |   1 -
> >  libavdevice/alldevices.c                          |   1 -
> >  libavdevice/utils.c                               |   2 +-
> >  libavformat/allformats.c                          |  32
> > ++++++++++++++-----
> >  libavformat/internal.h                            |   1 +
> >  libavradio/Makefile                               |  14 +++++++++
> >  libavradio/allradios.c                            |  65
> > +++++++++++++++++++++++++++++++++++++++
> >  libavradio/avradio.c                              |  32
> > +++++++++++++++++++
> >  libavradio/avradio.h                              | 121
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >  libavradio/internal.h                             |  28 +++++++++++++++++
> >  libavdevice/sdrindev.c => libavradio/sdrinradio.c |   2 +-
> >  {libavdevice => libavradio}/utils.c               |   4 +--
> >  libavradio/version.c                              |  45
> > +++++++++++++++++++++++++++
> >  libavradio/version.h                              |  45
> > +++++++++++++++++++++++++++
> >  libavradio/version_major.h                        |  36
> > ++++++++++++++++++++++
> >  libavutil/log.h                                   |   1 +
> >  tools/uncoded_frame.c                             |   4 +++
> >  24 files changed, 554 insertions(+), 23 deletions(-)
> >
> >
> >
> > I do not know if changes to the build system can be marged in git master or
> > if people agree to that at all.
> > But if this needs to be maintained in its current form, it will cause bugs
> > and alot of extra work over time
> >
> > the alternative would be to undo the libavradio thing and rather maintain
> > sdr as input device and demuxer in the libavradio repository
> >


> > Of course having the sdr input device and file demuxer in git master would
> > be the least amount of work
> >
> 
> Everyone is against this, pushing for it will not make it happen.

I think there where about 6 people who had varing levels of dislike to it.
Probably a few more. Thats not everyone

But i have not suggested that to be done now, i have not pushed for that at
all in the text or mail above.
Its just a statement of fact that it would be least work.
That statement, that its least work, has not been disputed by anyone

I mentioned this so people dont miss that the way its done now, has a
cost to it. The 2 repository approuch costs additional time to maintain

Also moving the whole libavradio to git master is not what this mail was
intended to suggest at all.

Thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Take away the freedom of one citizen and you will be jailed, take away
the freedom of all citizens and you will be congratulated by your peers
in Parliament.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2023-07-03 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  5:47 Michael Niedermayer
2023-07-03  8:54 ` Paul B Mahol
2023-07-03 14:17   ` Michael Niedermayer [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=20230703141747.GP1093384@pb2 \
    --to=michael@niedermayer.cc \
    --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