Hi, all.

per https://github.com/jclouds/jclouds/pull/6#issuecomment-18022286

jclouds includes a utility called scriptbuilder, which generates shell
scripts from other fragments.  We've not added license headers in the past
as these scripts are combined at runtime.

Ex. you can imagine that doing a command like below, the resulting shell
script would senselessly have multiple ASF license headers inlined.

runScript = new StatementList(installJDK, addRoot);

I seriously have objections about insisting adding license headers to
script fragments, not only from the efficiency concern, but also that it
adds a chance of hard-to-troubleshoot bugs.  For example, if we added
license headers to the script fragment for nohup, everything that uses
nohup will have an extra 14 lines of comments, or we'd have to write code
to remove it.  In cases where scriptBuilder is used as EC2 instance data,
it might push us over the limit.

Bottom-line question is:

Does the ASF require license header on inputs to commands, such as shell
script fragments that are inputs to ScriptBuilder?

-A

Reply via email to