> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of Rémi Denis- > Courmont > Sent: Samstag, 24. Mai 2025 18:02 > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/graphprint: Now, make it a > Killer-Feature! > > Le perjantaina 16. toukokuuta 2025, 3.54.21 Itä-Euroopan kesäaika Michael > Niedermayer a écrit : > > 1. lets all calm down, so far we have a civil and productive discussion > > maybe we can simply find a solution everyone is happy with! > > > > 2. all security issues must be fixed if there are some > > system() is security issue incarnate. > > > 3. there should be a configure flag to enable/disable the browser opening > > feature if it remains > > I don't see the point in having a configure flag. Either the TC finds the > feature > should not exist at all, and it should not exist at all. Or else, the feature > can stay as a disabled-by-default *run-time* flag and with the security issues > fixed. > > > 4. can system() be replaced by fork()+exec*() ? is that something people > > would prefer ? > > That is obviously far more adequate, though certain precautions are > potentially necessary such as resetting signal handling.
Which is what system() does already. The funny thing is, that if I would have copied glibc's implementation of system() - nobody would have objected. > > 5. this is a cool feature, i would use this if its available, that said > > if i had to manually open a browser with a given URL that would work > > for me too. > > If the feature outputs at a stable URL, keeping a tab open with auto or manual > refresh would work just as well, indeed, without the controversial feature. The idea is that each ffmpeg execution opens a new tab, so that you can compare between them. > > 7. as long as the discussion is nice and productive i think the TC is not > > the best path forward. If things degenerate into some mess then pas it to > > teh TC, yes > > It's been 6 days, and I don't see how to resolve this other than with a TC > decision. It was reverted on the same day already. Thanks sw _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
