On 07/11/16 12:38, David Spencer wrote:
[opt] libass, [env] ASS=yes|no [/opt], for ASS support,
> [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
> [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for IEC61883
* No parser exists for this language that you have just invented. Some
poor fool would have to write that. And it's one of the context
senstive languages (like HTML) that can't be parsed with regular
expressions -- see https://en.wikipedia.org/wiki/Chomsky_hierarchy
Subject for improvement.
* It's too complicated for newbies.
They might, but don't have to use it, as I suggested.
* It's going to look ugly in the README, and that really does matter.
Subject for improvement :-)
* It's incomplete: there are packages with option formats that this
language can't describe. Look at grass. Yet again, I repeat: don't
propose a solution until you have checked whether it works in the real
world. You're only ever looking at ffmpeg :(
-D.
As above :-)
I also suggested that, if it gets to complicated, you don't use it.
Handling simple cases is already an improvement.
--
Best regards,
Andrzej Telszewski
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
