[FFmpeg-devel] [PATCH 1/3] Use makeinfo to generate html doc for the new website

Andreas Cadhalpun andreas.cadhalpun at googlemail.com
Sun Jul 20 22:37:15 CEST 2014

On 20.07.2014 20:18, db0 company wrote:
> On Sun, Jul 20, 2014 at 7:25 PM, Andreas Cadhalpun
> <andreas.cadhalpun at googlemail.com> wrote:
>> On 20.07.2014 19:02, Timothy Gu wrote:
>>> Andreas,
>>>> Could somebody please add the source of the minified style.min.css?
>>> That is in the ffmpeg-web repo. All modifications to the CSS should be
>>> done there then backported here.
>> Ah, I see. But still, it would be nice to have the style.less in the release
>> tarball, to be able to generate the minified version from it.
>> Why not add it with a comment at the beginning that it should only be
>> modified in sync with the ffmpeg-web repo?
> Since the style.min.css is generated from the ffmpeg-web repo, I don't
> think adding its full version to the ffmpeg main repo would be a good
> idea because it would make people want to edit it. If they edit the
> generated version, the source is not edited.
> The README in the ffmpeg-web repo explains how the CSS file for the
> documentation is generated and recommend to update it in the main repo
> as well.
> A good solution in my opinion would be to explain somewhere in the
> main repo (maybe as a commented line at the beginning of the css
> file?) that the style.min.css file is generated from the ffmpeg-web
> repo and any modification of it should be on the ffmpeg-web repo only
> (ie on the sources, not on the generated file).

The other option would be to generate the style.min.css from the ffmpeg 
main repo and only copy the result to the ffmpeg-web repo.
That only has the disadvantage that the web stuff is then split between 
the repos.
In case you don't like that, a comment at the beginning of the css file 
would probably be sufficient for most purposes.

Best regards,

More information about the ffmpeg-devel mailing list