summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorA. Gordon <assafgordon@gmail.com>2014-08-19 23:59:56 (GMT)
committerA. Gordon <assafgordon@gmail.com>2014-08-19 23:59:56 (GMT)
commit825fc1162818e3f98320b89c5efe44d9faf7c171 (patch)
treee7fc92731e3bb0134ef6157a74f3b1d30acca54e
parenta89f5e1dd207a322656b9618e7ee78c4242e2849 (diff)
downloadgsv-eval-825fc1162818e3f98320b89c5efe44d9faf7c171.zip
gsv-eval-825fc1162818e3f98320b89c5efe44d9faf7c171.tar.gz
gsv-eval-825fc1162818e3f98320b89c5efe44d9faf7c171.tar.bz2
Perl script: improve wording fo 'compiled binary files'
-rwxr-xr-xgnu_savannah_eval.pl11
1 files changed, 9 insertions, 2 deletions
diff --git a/gnu_savannah_eval.pl b/gnu_savannah_eval.pl
index 3f2bcb6..c041dfe 100755
--- a/gnu_savannah_eval.pl
+++ b/gnu_savannah_eval.pl
@@ -964,10 +964,17 @@ EOF
The following files binary application files
(compiled objects, shared-libraries, executables, etc.).
Such files are usually created when compiling
-the source code in your package, and there's no need to include them in your package.
+the source code of your package, and there's no need to include them in your package.
+
+If the compiled files are not created from the source code of your project,
+they **can not** be hosted on GNU Savannah (GNU Savanna can only host binaries
+for which a complete and Free source code is available).
+
+In either case, it is best not to include compiled binaries in your project submission.
> NOTE:
-> Removing these files is not a strict requirement, but is highly recommended.
+> Removing these files is not a strict requirement, but is highly recommended.
+> Keeping compiled binary files in your project might delay the GNU Savannah evaluation.
EOF
print join("", map { " $_\n" } @binary_obj_files),"\n";