summaryrefslogtreecommitdiff
path: root/COPYING.EXTENSIONS
diff options
context:
space:
mode:
authorPerberos <[email protected]>2011-12-01 22:24:23 -0300
committerPerberos <[email protected]>2011-12-01 22:24:23 -0300
commit0e004c696b0e68b2cff37a4c3315b022a35eaf43 (patch)
tree43261e815529cb9518ed7be37af13b846af8b26b /COPYING.EXTENSIONS
downloadcaja-0e004c696b0e68b2cff37a4c3315b022a35eaf43.tar.bz2
caja-0e004c696b0e68b2cff37a4c3315b022a35eaf43.tar.xz
moving from https://github.com/perberos/mate-desktop-environment
Diffstat (limited to 'COPYING.EXTENSIONS')
-rw-r--r--COPYING.EXTENSIONS10
1 files changed, 10 insertions, 0 deletions
diff --git a/COPYING.EXTENSIONS b/COPYING.EXTENSIONS
new file mode 100644
index 00000000..d4ba7d8a
--- /dev/null
+++ b/COPYING.EXTENSIONS
@@ -0,0 +1,10 @@
+Caja extensions link against the libcaja-extenstions library which is
+is under the LGPL license. However, they also get loaded into the main
+caja program which is licensed under the GPL. So, extensions should not
+be incompatible with the LGPL or GPL.
+
+Some extensions are GPL but use some IPC mechanism like dbus to talk to a
+potentially non-GPL application. This is actually not such a bad design in
+general if your extension is doing a lot of work, as running as a caja
+extension with all its issues (no synchronous i/o, can't control of the
+context your code runs in, etc) can be kind of a pain.