summaryrefslogtreecommitdiff
path: root/COPYING.EXTENSIONS
diff options
context:
space:
mode:
authorAlexander Larsson <alexl@redhat.com>2009-05-27 11:05:56 +0200
committerAlexander Larsson <alexl@redhat.com>2009-05-27 11:06:31 +0200
commit7d9b6812d006d9aeecfb33d072cb382184fb901b (patch)
tree5b94021234a0e848b51751729020add84550af3e /COPYING.EXTENSIONS
parent74782b711adccfb85273ac38484e4adac8e010b4 (diff)
downloadnautilus-7d9b6812d006d9aeecfb33d072cb382184fb901b.tar.gz
Add COPYING.EXTENSIONS clarifying some extension license issues
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 000000000..22b47e655
--- /dev/null
+++ b/COPYING.EXTENSIONS
@@ -0,0 +1,10 @@
+Nautilus extensions link against the libnautilus-extenstions library which is
+is under the LGPL license. However, they also get loaded into the main
+nautilus 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 nautilus
+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.