summaryrefslogtreecommitdiff
path: root/COMPLIANCE
diff options
context:
space:
mode:
authorStefan Schmidt <s.schmidt@samsung.com>2019-11-01 09:35:09 +0100
committerCedric BAIL <cedric.bail@free.fr>2019-12-04 12:21:24 -0800
commitf3d9b8ee703621cfbb52a03d346335148318af7a (patch)
tree38e0f640c8ed31c717668faa64be419fa6c07905 /COMPLIANCE
parent003ce06e85ba0f1597a26405ead92f2e01607177 (diff)
downloadefl-f3d9b8ee703621cfbb52a03d346335148318af7a.tar.gz
esacpe: remove library from tree
This has not been used for a while and is not even buildable after our switch to meson. It was a niche to start with given that it needed the PS3 OS to run on. I asked for any remaining users at EDD and on the list but heard nothing. Time to remove. Signed-off-by: Stefan Schmidt <s.schmidt@samsung.com> Reviewed-by: Cedric BAIL <cedric.bail@free.fr> Differential Revision: https://phab.enlightenment.org/D10778
Diffstat (limited to 'COMPLIANCE')
-rw-r--r--COMPLIANCE4
1 files changed, 1 insertions, 3 deletions
diff --git a/COMPLIANCE b/COMPLIANCE
index ecd0c343ec..1df68cfb01 100644
--- a/COMPLIANCE
+++ b/COMPLIANCE
@@ -39,9 +39,7 @@ pieces of information you will need.
Q. Do I need to make the source public of libraries or applications that I
build on top of EFL?
-A. No, UNLESS you use the escape library. Escape is GPL. This is ONLY
-needed for PS3 development, so unless you are doing this, it is not
-relevant.
+A. No
Q. Do I need to provide the source for EFL?
A. Yes. In general you do. If you are shipping any of the binaries or