Browse files

moving from https://github.com/perberos/mate-desktop-environment

  • Loading branch information...
0 parents commit 0e004c696b0e68b2cff37a4c3315b022a35eaf43 @perberos perberos committed Dec 1, 2011
Showing with 19,674 additions and 0 deletions.
  1. +60 −0 AUTHORS
  2. +351 −0 COPYING
  3. +355 −0 COPYING-DOCS
  4. +10 −0 COPYING.EXTENSIONS
  5. +482 −0 COPYING.LIB
  6. 0 ChangeLog
  7. +57 −0 HACKING
  8. +365 −0 INSTALL
  9. +23 −0 MAINTAINERS
  10. +44 −0 Makefile.am
  11. +1 −0 Makefile.shared
  12. +1,713 −0 NEWS
  13. +31 −0 README
  14. +68 −0 README.commits
  15. +621 −0 THANKS
  16. +19 −0 TODO
  17. +27 −0 acconfig.h
  18. +1,812 −0 aclocal.m4
  19. +1 −0 add-include-prefix
  20. +25 −0 autogen.sh
  21. +1,501 −0 config.guess
  22. +185 −0 config.h.in
  23. +1,705 −0 config.sub
  24. +483 −0 configure.in
  25. +2 −0 cut-n-paste-code/Makefile.am
  26. +646 −0 cut-n-paste-code/Makefile.in
  27. +21 −0 cut-n-paste-code/README
  28. +46 −0 cut-n-paste-code/libegg/Makefile.am
  29. +657 −0 cut-n-paste-code/libegg/Makefile.in
  30. +1,477 −0 cut-n-paste-code/libegg/eggdesktopfile.c
  31. +166 −0 cut-n-paste-code/libegg/eggdesktopfile.h
  32. +57 −0 cut-n-paste-code/libegg/eggsmclient-private.h
  33. +1,371 −0 cut-n-paste-code/libegg/eggsmclient-xsmp.c
  34. +602 −0 cut-n-paste-code/libegg/eggsmclient.c
  35. +123 −0 cut-n-paste-code/libegg/eggsmclient.h
  36. +415 −0 cut-n-paste-code/libegg/eggtreemultidnd.c
  37. +78 −0 cut-n-paste-code/libegg/eggtreemultidnd.h
  38. +25 −0 cut-n-paste-code/libegg/update-from-egg.sh
  39. +54 −0 data/Makefile.am
  40. +76 −0 data/browser.xml
  41. +14 −0 data/caja-autorun-software.desktop.in.in
  42. +15 −0 data/caja-browser.desktop.in.in
  43. +15 −0 data/caja-computer.desktop.in.in
  44. +2 −0 data/caja-extras.placeholder
  45. +14 −0 data/caja-file-management-properties.desktop.in.in
  46. +15 −0 data/caja-folder-handler.desktop.in.in
  47. +14 −0 data/caja-home.desktop.in.in
  48. +2 −0 data/caja-suggested.placeholder
  49. +17 −0 data/caja.desktop.in.in
  50. +8 −0 data/caja.xml.in
  51. +86 −0 data/icons/Makefile.am
  52. BIN data/icons/hicolor_apps_16x16_caja.png
  53. +262 −0 data/icons/hicolor_apps_16x16_caja.svg
  54. BIN data/icons/hicolor_apps_22x22_caja.png
  55. +323 −0 data/icons/hicolor_apps_22x22_caja.svg
  56. BIN data/icons/hicolor_apps_24x24_caja.png
  57. BIN data/icons/hicolor_apps_32x32_caja.png
  58. +314 −0 data/icons/hicolor_apps_32x32_caja.svg
  59. +275 −0 data/icons/hicolor_apps_scalable_caja.svg
  60. BIN data/icons/hicolor_emblems_16x16_emblem-note.png
  61. BIN data/icons/hicolor_emblems_24x24_emblem-note.png
  62. BIN data/icons/hicolor_emblems_48x48_emblem-note.png
  63. +39 −0 data/patterns/Makefile.am
  64. BIN data/patterns/blue_gray_rough.png
  65. BIN data/patterns/blue_ridge.png
  66. BIN data/patterns/blue_type.png
  67. BIN data/patterns/brushed_metal.png
  68. BIN data/patterns/burlap.jpg
  69. BIN data/patterns/camouflage.png
  70. BIN data/patterns/chalk.jpg
  71. BIN data/patterns/cork.png
  72. BIN data/patterns/countertop.png
  73. BIN data/patterns/dark-mate.jpg
  74. BIN data/patterns/dots.png
  75. BIN data/patterns/fibers.png
  76. BIN data/patterns/fleur_de_lis.png
  77. BIN data/patterns/floral.png
  78. BIN data/patterns/fossil.png
  79. BIN data/patterns/green_weave.png
  80. BIN data/patterns/ice.png
  81. BIN data/patterns/manila_paper.png
  82. BIN data/patterns/mate.jpg
  83. BIN data/patterns/moss_ridge.png
  84. BIN data/patterns/numbers.png
  85. BIN data/patterns/ocean_stripes.png
  86. BIN data/patterns/purple_marble.png
  87. BIN data/patterns/reset.png
  88. BIN data/patterns/ridged_paper.png
  89. BIN data/patterns/rough_paper.png
  90. BIN data/patterns/sky_ridge.png
  91. BIN data/patterns/snow_ridge.png
  92. BIN data/patterns/stucco.jpg
  93. BIN data/patterns/terracotta.png
  94. BIN data/patterns/wavy_white.png
  95. +630 −0 depcomp
  96. +41 −0 distro/archlinux/PKGBUILD
  97. +28 −0 distro/archlinux/mate-file-manager.install
  98. +36 −0 distro/ubuntu/build
  99. +15 −0 distro/ubuntu/postinst
  100. +10 −0 distro/ubuntu/postrm
  101. +8 −0 distro/ubuntu/preinst
  102. +11 −0 distro/ubuntu/prerm
  103. +25 −0 docs/Makefile.am
  104. +160 −0 docs/architecture.txt
  105. +50 −0 docs/caja-connect-server.1
  106. +49 −0 docs/caja-file-management-properties.1
  107. BIN docs/caja-internals.pdf
  108. BIN docs/caja-internals.sxw
  109. +255 −0 docs/caja-io.txt
  110. +77 −0 docs/caja.1
  111. +7 −0 docs/caja.faq
  112. +92 −0 docs/dnd.txt
  113. +112 −0 docs/key_mouse_navigation.txt
  114. BIN docs/load-states.dia
  115. +167 −0 docs/recommended-books.html
  116. +1 −0 docs/reference/Makefile.am
  117. +646 −0 docs/reference/Makefile.in
  118. +84 −0 docs/reference/libcaja-extension/Makefile.am
Sorry, we could not display the entire diff because too many files (709) changed.
60 AUTHORS
@@ -0,0 +1,60 @@
+Caja 2.22 version by:
+Martin Wehner <martin.wehner@gmail.com>
+Alex Larsson <alexl@redhat.com
+Christian Neumair <cneumair@gnome.org>
+Cosimo Cecchi <cosimoc@gnome.org>
+David Zeuthen <davidz@redhat.com>
+
+Caja 2.4 version by:
+
+Alex Larsson <alexl@redhat.com>
+Dave Camp <dave@ximian.com>
+Soren Sandmann <sandmann@daimi.au.dk>
+Jürg Billeter <j@bitron.ch>
+
+Caja 2.2 version by:
+
+Alex Larsson <alexl@redhat.com>
+Dave Camp <dave@ximian.com>
+James Willcox <jwillcox@gnome.org>
+Jan Arne Petersen <jpetersen@uni-bonn.de>
+Mark McLoughlin <mark@skynet.ie>
+
+Mate 2 conversion by:
+
+Darin Adler <darin@bentspoon.com>
+Anders Carlsson <andersca@gnu.org>
+Michael Meeks <michael@ximian.com>
+Alex Larsson <alexl@redhat.com>
+Jacob Berkman <jacob@ximian.com>
+*** need to decide who else to add here ***
+
+Original version by the Caja 1.0 team:
+
+Ali Abdin <aliabdin@aucegypt.edu>
+Andy Hertzfeld <andy@differnet.com>
+Arlo Rose <arlo@eazel.com>
+Darin Adler <darin@bentspoon.com>
+Eli Goldberg <eli@eazel.com>
+Elliot Lee <sopwith@redhat.com>
+Eskil Heyn Olsen <eskil@eazel.com>
+Ettore Perazzoli <ettore@ximian.com>
+Gene Z. Ragan <gzr@eazel.com>
+George Lebl <jirka@5z.com>
+Ian McKellar <ian@eazel.com>
+John Harper <jsh@pixelslut.com>
+John Sullivan <sullivan@eazel.com>
+Josh Barrow <drleary@mac.com>
+J Shane Culpepper <pepper@eazel.com>
+Maciej Stachowiak <mjs@noisehavoc.org>
+Mathieu Lacage <mathieu@eazel.com>
+Mike Engber <engber@eazel.com>
+Mike Fleming <mfleming@eazel.com>
+Pavel Cisler <pavel@eazel.com>
+Ramiro Estrugo <ramiro@fateware.com>
+Raph Levien <raph@acm.org>
+Rebecca Schulman <rebecka@eazel.com>
+Robey Pointer <robey@eazel.com>
+Robin * Slomkowski <rslomkow@eazel.com>
+Seth Nickell <snickell@stanford.edu>
+Susan Kare <susan@eazel.com>
351 COPYING
@@ -0,0 +1,351 @@
+**********************************************************************
+The following license applies to the Caja software but does not
+apply to the Eazel Trademarks. Please read the TRADEMARK_NOTICE file
+for licensing information about the Eazel Trademarks.
+**********************************************************************
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
355 COPYING-DOCS
@@ -0,0 +1,355 @@
+ GNU Free Documentation License
+ Version 1.1, March 2000
+
+ Copyright (C) 2000 Free Software Foundation, Inc.
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+0. PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+written document "free" in the sense of freedom: to assure everyone
+the effective freedom to copy and redistribute it, with or without
+modifying it, either commercially or noncommercially. Secondarily,
+this License preserves for the author and publisher a way to get
+credit for their work, while not being considered responsible for
+modifications made by others.
+
+This License is a kind of "copyleft", which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+
+
+1. APPLICABILITY AND DEFINITIONS
+
+This License applies to any manual or other work that contains a
+notice placed by the copyright holder saying it can be distributed
+under the terms of this License. The "Document", below, refers to any
+such manual or work. Any member of the public is a licensee, and is
+addressed as "you".
+
+A "Modified Version" of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+A "Secondary Section" is a named appendix or a front-matter section of
+the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall subject
+(or to related matters) and contains nothing that could fall directly
+within that overall subject. (For example, if the Document is in part a
+textbook of mathematics, a Secondary Section may not explain any
+mathematics.) The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+The "Invariant Sections" are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License.
+
+The "Cover Texts" are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License.
+
+A "Transparent" copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, whose contents can be viewed and edited directly and
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters. A copy made in an otherwise Transparent file
+format whose markup has been designed to thwart or discourage
+subsequent modification by readers is not Transparent. A copy that is
+not "Transparent" is called "Opaque".
+
+Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, LaTeX input format, SGML
+or XML using a publicly available DTD, and standard-conforming simple
+HTML designed for human modification. Opaque formats include
+PostScript, PDF, proprietary formats that can be read and edited only
+by proprietary word processors, SGML or XML for which the DTD and/or
+processing tools are not generally available, and the
+machine-generated HTML produced by some word processors for output
+purposes only.
+
+The "Title Page" means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in
+formats which do not have any title page as such, "Title Page" means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+
+2. VERBATIM COPYING
+
+You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License. You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute. However, you may accept
+compensation in exchange for copies. If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+
+3. COPYING IN QUANTITY
+
+If you publish printed copies of the Document numbering more than 100,
+and the Document's license notice requires Cover Texts, you must enclose
+the copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover. Both covers must also clearly and legibly identify
+you as the publisher of these copies. The front cover must present
+the full title with all words of the title equally prominent and
+visible. You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a publicly-accessible computer-network location containing a complete
+Transparent copy of the Document, free of added material, which the
+general network-using public has access to download anonymously at no
+charge using public-standard network protocols. If you use the latter
+option, you must take reasonably prudent steps, when you begin
+distribution of Opaque copies in quantity, to ensure that this
+Transparent copy will remain thus accessible at the stated location
+until at least one year after the last time you distribute an Opaque
+copy (directly or through your agents or retailers) of that edition to
+the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+
+
+4. MODIFICATIONS
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it. In addition, you must do these things in the Modified Version:
+
+A. Use in the Title Page (and on the covers, if any) a title distinct
+ from that of the Document, and from those of previous versions
+ (which should, if there were any, be listed in the History section
+ of the Document). You may use the same title as a previous version
+ if the original publisher of that version gives permission.
+B. List on the Title Page, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the Modified
+ Version, together with at least five of the principal authors of the
+ Document (all of its principal authors, if it has less than five).
+C. State on the Title page the name of the publisher of the
+ Modified Version, as the publisher.
+D. Preserve all the copyright notices of the Document.
+E. Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+F. Include, immediately after the copyright notices, a license notice
+ giving the public permission to use the Modified Version under the
+ terms of this License, in the form shown in the Addendum below.
+G. Preserve in that license notice the full lists of Invariant Sections
+ and required Cover Texts given in the Document's license notice.
+H. Include an unaltered copy of this License.
+I. Preserve the section entitled "History", and its title, and add to
+ it an item stating at least the title, year, new authors, and
+ publisher of the Modified Version as given on the Title Page. If
+ there is no section entitled "History" in the Document, create one
+ stating the title, year, authors, and publisher of the Document as
+ given on its Title Page, then add an item describing the Modified
+ Version as stated in the previous sentence.
+J. Preserve the network location, if any, given in the Document for
+ public access to a Transparent copy of the Document, and likewise
+ the network locations given in the Document for previous versions
+ it was based on. These may be placed in the "History" section.
+ You may omit a network location for a work that was published at
+ least four years before the Document itself, or if the original
+ publisher of the version it refers to gives permission.
+K. In any section entitled "Acknowledgements" or "Dedications",
+ preserve the section's title, and preserve in the section all the
+ substance and tone of each of the contributor acknowledgements
+ and/or dedications given therein.
+L. Preserve all the Invariant Sections of the Document,
+ unaltered in their text and in their titles. Section numbers
+ or the equivalent are not considered part of the section titles.
+M. Delete any section entitled "Endorsements". Such a section
+ may not be included in the Modified Version.
+N. Do not retitle any existing section as "Endorsements"
+ or to conflict in title with any Invariant Section.
+
+If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant. To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+You may add a section entitled "Endorsements", provided it contains
+nothing but endorsements of your Modified Version by various
+parties--for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version. Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity. If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
+
+5. COMBINING DOCUMENTS
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice.
+
+The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy. If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+In the combination, you must combine any sections entitled "History"
+in the various original documents, forming one section entitled
+"History"; likewise combine any sections entitled "Acknowledgements",
+and any sections entitled "Dedications". You must delete all sections
+entitled "Endorsements."
+
+
+6. COLLECTIONS OF DOCUMENTS
+
+You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+
+You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+
+
+7. AGGREGATION WITH INDEPENDENT WORKS
+
+A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, does not as a whole count as a Modified Version
+of the Document, provided no compilation copyright is claimed for the
+compilation. Such a compilation is called an "aggregate", and this
+License does not apply to the other self-contained works thus compiled
+with the Document, on account of their being thus compiled, if they
+are not themselves derivative works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one quarter
+of the entire aggregate, the Document's Cover Texts may be placed on
+covers that surround only the Document within the aggregate.
+Otherwise they must appear on covers around the whole aggregate.
+
+
+8. TRANSLATION
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections. You may include a
+translation of this License provided that you also include the
+original English version of this License. In case of a disagreement
+between the translation and the original English version of this
+License, the original English version will prevail.
+
+
+9. TERMINATION
+
+You may not copy, modify, sublicense, or distribute the Document except
+as expressly provided for under this License. Any other attempt to
+copy, modify, sublicense or distribute the Document is void, and will
+automatically terminate your rights under this License. However,
+parties who have received copies, or rights, from you under this
+License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+
+10. FUTURE REVISIONS OF THIS LICENSE
+
+The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns. See
+http://www.gnu.org/copyleft/.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License "or any later version" applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation. If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation.
+
+
+ADDENDUM: How to use this License for your documents
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
+ Copyright (c) YEAR YOUR NAME.
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.1
+ or any later version published by the Free Software Foundation;
+ with the Invariant Sections being LIST THEIR TITLES, with the
+ Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
+ A copy of the license is included in the section entitled "GNU
+ Free Documentation License".
+
+If you have no Invariant Sections, write "with no Invariant Sections"
+instead of saying which ones are invariant. If you have no
+Front-Cover Texts, write "no Front-Cover Texts" instead of
+"Front-Cover Texts being LIST"; likewise for Back-Cover Texts.
+
+If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
10 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.
482 COPYING.LIB
@@ -0,0 +1,482 @@
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1991 Free Software Foundation, Inc.
+ 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the library GPL. It is
+ numbered 2 because it goes with version 2 of the ordinary GPL.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Library General Public License, applies to some
+specially designated Free Software Foundation software, and to any
+other libraries whose authors decide to use it. You can use it for
+your libraries, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if
+you distribute copies of the library, or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link a program with the library, you must provide
+complete object files to the recipients so that they can relink them
+with the library, after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ Our method of protecting your rights has two steps: (1) copyright
+the library, and (2) offer you this license which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ Also, for each distributor's protection, we want to make certain
+that everyone understands that there is no warranty for this free
+library. If the library is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original
+version, so that any problems introduced by others will not reflect on
+the original authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that companies distributing free
+software will individually obtain patent licenses, thus in effect
+transforming the program into proprietary software. To prevent this,
+we have made it clear that any patent must be licensed for everyone's
+free use or not licensed at all.
+
+ Most GNU software, including some libraries, is covered by the ordinary
+GNU General Public License, which was designed for utility programs. This
+license, the GNU Library General Public License, applies to certain
+designated libraries. This license is quite different from the ordinary
+one; be sure to read it in full, and don't assume that anything in it is
+the same as in the ordinary license.
+
+ The reason we have a separate public license for some libraries is that
+they blur the distinction we usually make between modifying or adding to a
+program and simply using it. Linking a program with a library, without
+changing the library, is in some sense simply using the library, and is
+analogous to running a utility program or application program. However, in
+a textual and legal sense, the linked executable is a combined work, a
+derivative of the original library, and the ordinary General Public License
+treats it as such.
+
+ Because of this blurred distinction, using the ordinary General
+Public License for libraries did not effectively promote software
+sharing, because most developers did not use the libraries. We
+concluded that weaker conditions might promote sharing better.
+
+ However, unrestricted linking of non-free programs would deprive the
+users of those programs of all benefit from the free status of the
+libraries themselves. This Library General Public License is intended to
+permit developers of non-free programs to use free libraries, while
+preserving your freedom as a user of such programs to change the free
+libraries that are incorporated in them. (We have not seen how to achieve
+this as regards changes in header files, but we have achieved it as regards
+changes in the actual functions of the Library.) The hope is that this
+will lead to faster development of free libraries.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, while the latter only
+works together with the library.
+
+ Note that it is possible for a library to be covered by the ordinary
+General Public License rather than by this special one.
+
+ GNU LIBRARY GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library which
+contains a notice placed by the copyright holder or other authorized
+party saying it may be distributed under the terms of this Library
+General Public License (also called "this License"). Each licensee is
+addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also compile or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ c) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ d) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the source code distributed need not include anything that is normally
+distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Library General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ Appendix: How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the library's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Library General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Library General Public License for more details.
+
+ You should have received a copy of the GNU Library General Public
+ License along with this library; if not, write to the Free
+ Software Foundation, Inc., 59 Temple Place - Suite 330, Boston,
+ MA 02111-1307, USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
0 ChangeLog
No changes.
57 HACKING
@@ -0,0 +1,57 @@
+Hacking on Caja
+-------------------
+
+The Caja source tree is available from MATE git (git.gnome.org) and
+in releases on the MATE FTP site
+(http://ftp.gnome.org/pub/MATE/sources/caja/).
+
+If you plan to hack on Caja, please make sure you work from the
+Git version. The Git version can be checked from the MATE git server.
+See http://live.gnome.org/Git for details on how to get started with
+MATE Git. For details on how Caja uses git, see the README.commits
+file.
+
+If you want to contribute in development discussions, please send mail
+to the caja mailing list: <caja-list@gnome.org>. Archives and
+subscription information are available at
+http://mail.gnome.org/mailman/listinfo/caja-list
+
+
+Submitting Patches
+------------------
+
+If you've been working on a change to Caja and want to propose it
+for inclusion, you have to generate a patch and submit it for review
+by the maintainers.
+
+Patches should be made with 'git format-patch -M'
+and should conform to Caja coding style as described in
+docs/style-guide.html. We are pretty strict about coding style, so
+please make sure you follow the style guide to avoid unnecessary
+work on both sides when reviewing the patch.
+
+The best way to submit a patch for review is to post it on the mailing
+list. That way everyone sees it and can take part in the following
+discussion about it. Sometimes people also attach patches to bugs in
+bugzilla (http://bugzilla.gnome.org, product 'caja'). If you do
+this, please send a mail to the list saying you did so, because it is
+very easy for the bugzilla email to get lost in all the bugzilla
+reports, and only the people CCd on the bug can partake in the
+discussion. When attaching bugs to bugzilla from git the git-bz
+command can be helpful, see:
+http://blog.fishsoup.net/2008/11/16/git-bz-bugzilla-subcommand-for-git/
+
+The Caja maintainers do their best to review patches and help
+developers that want to work on something, however we are often
+swamped in work and can miss an email or just forget to answer
+it. Don't be afraid of reposting your patches after a while, or poking
+us about the status of them.
+
+Also, if you're planning to do large changes, please take them up for
+discussion on the list first. If you get feedback early it is much
+easier to integrate it into your work.
+
+If your patch adds non-trivial strings, please ask for a string review
+from the i18n team before committing the changes. Strings should avoid
+contractions, and stay consistent with other strings already in Caja.
+Please reuse strings within Caja where it makes sense to do so.
365 INSTALL
@@ -0,0 +1,365 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008, 2009 Free Software Foundation, Inc.
+
+ Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved. This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+ Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package. The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package. Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below. The lack of an optional feature in a given package is not
+necessarily a bug. More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+ The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions. Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+ If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release. If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+ The simplest way to compile this package is:
+
+ 1. `cd' to the directory containing the package's source code and type
+ `./configure' to configure the package for your system.
+
+ Running `configure' might take a while. While running, it prints
+ some messages telling which features it is checking for.
+
+ 2. Type `make' to compile the package.
+
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package, generally using the just-built uninstalled binaries.
+
+ 4. Type `make install' to install the programs and any data files and
+ documentation. When installing into a prefix owned by root, it is
+ recommended that the package be configured and built as a regular
+ user, and only the `make install' phase executed with root
+ privileges.
+
+ 5. Optionally, type `make installcheck' to repeat any self-tests, but
+ this time using the binaries in their final installed location.
+ This target does not install anything. Running this target as a
+ regular user, particularly if the prior `make install' required
+ root privileges, verifies that the installation completed
+ correctly.
+
+ 6. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+ 7. Often, you can also type `make uninstall' to remove the installed
+ files again. In practice, not all packages have tested that
+ uninstallation works correctly, even though it is required by the
+ GNU Coding Standards.
+
+ 8. Some packages, particularly those that use Automake, provide `make
+ distcheck', which can by used by developers to test that all other
+ targets like `make install' and `make uninstall' work correctly.
+ This target is generally not run by end users.
+
+Compilers and Options
+=====================
+
+ Some systems require unusual options for compilation or linking that
+the `configure' script does not know about. Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+ You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you can use GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'. This
+is known as a "VPATH" build.
+
+ With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory. After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+ On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple `-arch' options to the
+compiler but only a single `-arch' option to the preprocessor. Like
+this:
+
+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CPP="gcc -E" CXXCPP="g++ -E"
+
+ This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the `lipo' tool if you have problems.
+
+Installation Names
+==================
+
+ By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc. You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX', where PREFIX must be an
+absolute file name.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them. In general, the
+default for these options is expressed in terms of `${prefix}', so that
+specifying just `--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+ The most portable way to affect installation locations is to pass the
+correct locations to `configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+`make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+ The first method involves providing an override variable for each
+affected directory. For example, `make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+`${prefix}'. Any directories that were specified during `configure',
+but not in terms of `${prefix}', must each be overridden at install
+time for the entire installation to be relocated. The approach of
+makefile variable overrides for each directory variable is required by
+the GNU Coding Standards, and ideally causes no recompilation.
+However, some platforms have known limitations with the semantics of
+shared libraries that end up requiring recompilation when using this
+method, particularly noticeable in packages that use GNU Libtool.
+
+ The second method involves providing the `DESTDIR' variable. For
+example, `make install DESTDIR=/alternate/directory' will prepend
+`/alternate/directory' before all installation names. The approach of
+`DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters. On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of `${prefix}'
+at `configure' time.
+
+Optional Features
+=================
+
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+ Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+ Some packages offer the ability to configure how verbose the
+execution of `make' will be. For these packages, running `./configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with `make V=1'; while running `./configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with `make V=0'.
+
+Particular systems
+==================
+
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU
+CC is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+ ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+a workaround. If GNU CC is not installed, it is therefore recommended
+to try
+
+ ./configure CC="cc"
+
+and if that doesn't work, try
+
+ ./configure CC="cc -nodtk"
+
+ On Solaris, don't put `/usr/ucb' early in your `PATH'. This
+directory contains several dysfunctional programs; working variants of
+these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
+in your `PATH', put it _after_ `/usr/bin'.
+
+ On Haiku, software installed for all users goes in `/boot/common',
+not `/usr/local'. It is recommended to use the following options:
+
+ ./configure --prefix=/boot/common
+
+Specifying the System Type
+==========================
+
+ There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on. Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS
+ KERNEL-OS
+
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+ If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists. Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+ Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug. Until the bug is fixed you can use this workaround:
+
+ CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+`configure' Invocation
+======================
+
+ `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+ Print a summary of all of the options to `configure', and exit.
+
+`--help=short'
+`--help=recursive'
+ Print a summary of the options unique to this package's
+ `configure', and exit. The `short' variant lists options used
+ only in the top level, while the `recursive' variant lists options
+ also present in any nested packages.
+
+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to `/dev/null' (any error
+ messages will still be shown).
+
+`--srcdir=DIR'
+ Look for the package's source code in directory DIR. Usually
+ `configure' can determine that directory automatically.
+
+`--prefix=DIR'
+ Use DIR as the installation prefix. *note Installation Names::
+ for more details, including other options available for fine-tuning
+ the installation locations.
+
+`--no-create'
+`-n'
+ Run the configure checks, but stop before creating any output
+ files.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
23 MAINTAINERS
@@ -0,0 +1,23 @@
+Alex Larsson
+E-mail: alexl@redhat.com
+Userid: alexl
+
+Dave Camp
+E-mail: dave@novell.com
+Userid: campd
+
+Martin Wehner
+E-mail: martin.wehner@gmail.com
+Userid: mwehner
+
+Christian Neumair
+E-mail: cneumair@gnome.org
+Userid: cneumair
+
+Andrew Walton
+E-mail: awalton@gnome.org
+Userid: awalton
+
+Cosimo Cecchi
+E-mail: cosimoc@gnome.org
+Userid: cosimoc
44 Makefile.am
@@ -0,0 +1,44 @@
+include $(top_srcdir)/Makefile.shared
+
+SUBDIRS = \
+ eel \
+ libcaja-extension \
+ cut-n-paste-code \
+ libcaja-private \
+ src \
+ test \
+ po \
+ data \
+ icons \
+ docs \
+ $(NULL)
+
+EXTRA_DIST= \
+ COPYING.LIB \
+ COPYING.EXTENSIONS \
+ COPYING-DOCS \
+ HACKING \
+ MAINTAINERS \
+ README.commits \
+ intltool-extract.in \
+ intltool-merge.in \
+ intltool-update.in \
+ Makefile.shared \
+ add-include-prefix \
+ $(NULL)
+
+DISTCLEANFILES = \
+ intltool-extract \
+ intltool-merge \
+ intltool-update
+
+DISTCHECK_CONFIGURE_FLAGS = --disable-update-mimedb --enable-gtk-doc
+
+ACLOCAL_AMFLAGS = -I m4
+
+distclean-local:
+ if test "$(srcdir)" = "."; then :; else \
+ rm -f ChangeLog; \
+ fi
+
+.PHONY: ChangeLog
1 Makefile.shared
@@ -0,0 +1 @@
+NULL =
1,713 NEWS
@@ -0,0 +1,1713 @@
+Major changes in 2.32.0 are:
+* Fix places sidebar sometimes not changing location
+ when clicking on a place
+* Fix various crashers
+* Translation updates
+
+Major changes in 2.31.92 are:
+* String fixes for the file conflict dialog
+* Add a border around infobars
+* Fix a regression when copy/pasting in list view
+* Re-use libunique instead of GApplication
+* Drop GDK_DISABLE_DEPRECATED cflag, as we don't want to cope with
+ recent GDK 2.22 deprecations for the 2.32 branch
+
+Major changes in 2.31.90 are:
+* Don't make pathbar buttons disappear when deleting a folder
+* Remove useless unique-1.0 dependency
+* Don't use deprecated GtkNotebookPage
+* Translation updates
+
+Major changes in 2.31.6 are:
+* This release is based on 2.30.1
+* A long list of fixes have been backported from the master branch,
+ including:
+ * Expand and collapse folders with +/- in list view
+ * Rename .desktop files also change their name on disk
+ * Support overriding .mate2 directory
+ * Save passwords for the session by default
+ * Remove deleted folders from the pathbar
+ * Replace libunique with GApplication
+ * Don't show 'File Browser' anymore in the window title
+ * Port to GDBus
+ * Change the default order for files in special directories
+ * Support relative paths in the location entry/dialog.
+ * Use folder icons as window icons in browser and spatial mode
+ * Add 'Trashed On' and 'Original Location' columns in the trash
+ * Implement transparent icons for cut files
+ * Change default thumbnail size
+ * Fix a number of bugs related to bookmarks
+ * New dialog to handle conflicts within file copy/move operations
+ * New button in the trashbar to restore selected items
+ * Use async I/O to save .gtk-bookmarks
+ * Fix a number of issues related to DnD in the places sidebar
+ * New icon for audio preview
+ * Don't show Unmount when showing Eject/Safe Removal
+ * Bump libcaja-extension API version
+ * Fix a number of UI glitches
+* Translation updates
+
+Major changes in 2.30.1 are:
+* Translation updates
+* Support for tracker 0.8.0
+* Fix crashes
+* Fix emblem scaling in zoomed view
+* Fix sensitivity of split-view related menu items
+* Control-L closes the extra view first, not the window
+
+Major changes in 2.30.0 are:
+* By default, don't exit with last window even if desktop is
+ not visible. This way we still run to handle e.g. volume
+ monitoring. If you don't want this, change
+ /apps/caja/preferences/exit_with_last_window
+ to True in mateconf
+* Don't show weird border around desktop
+* Correctly put focus on view for new windows
+* Extra view does not get focus when created
+* Add nicer thumbnail border
+* Fix crash when hiding search bar
+* Fix build on sun compiler
+* Support AIFF for audio preview
+* Translation updates
+
+Major changes in 2.29.92.1 are:
+* Fix compilation due to deprecated GTK_WIDGET_STATE symbol
+* Fix libm linking
+* Updated Portuguese translation
+
+Major changes in 2.29.92 are:
+* Make view default focus in new windows
+* Put tabs at the top again
+* Don't use deprecated gtk widgets
+* Allow Alt-<num> to switch tabs
+* Dynamically load tracker support
+* Don't auto-close the window you initiated an unmount in
+
+Major changes in 2.29.91 are:
+* Make it possible to have backgrounds spanning multiple monitors.
+* Better handling of closing windows when device is unmounted
+* Use GtkSpinner instead of custom widget
+* Translation updates
+
+Major changes in 2.29.90 are:
+* Fix copy-pasted tooltip string
+* Translation updates
+
+Major changes in 2.29.2 are:
+* Align sidebar header and location bar
+* Remove tabs menu
+* Update translations
+
+Major changes in 2.29.1 are:
+* Make browser mode the default
+* Add split view mode
+* Browser UI reorganization
+* Better background support on multi-monitor setups
+* Support new "default location" on mounts (supported by ftp and sftp)
+* Add extension api to lookup CajaFileInfo objects
+* Make the search toolbar button a toggle button
+* Ctrl+shift does multiple range selection in list view
+
+Major changes in 2.28.0 are:
+* Translation updates
+* Don't load non-images for thumbnailing when zoomed
+* Made desktop window a native X window for nicer redrawing
+* Fix leaks
+
+Major changes in 2.27.92 are:
+* Fix crash on logout
+* Translation updates
+* Always show app icon in open with popup menu
+* fix duplicate id in ui file
+* Fix warning in new power manager inhibiting
+
+Major changes in 2.27.91 are:
+* Migrate old-style caja metadata to gvfs metadata
+* Fix viewing of very small image files
+* Respect disable_command_line option
+* Reverse mouse button used for back/forward to same as firefox
+* Always show menu icons for menu items representing files
+* Inhibit suspend during file operations
+* Cancel audio preview when deleting the previewed file
+
+Major changes in 2.27.4 are:
+* Add support for starting and stopping drives
+* Use the new GVfs metadata framework
+* Support new style unmount operations; this will provide a nice dialog when
+ unmounting a busy drive mount
+* Add application icons to the Open With context menu
+* Reload xdg-user-dirs according to the user preferences
+
+Major changes in 2.27.2 are:
+* Support ctrl-drop in list view
+* Allow user defined keyboard shortcuts for extension items
+* Fix crash on click on toolbar
+* Fix crash on entering empty location
+* Added daemon-mode (don't exit with last window)
+* Display info about the selected item in the information sidebar
+* Sort applications in open with
+
+Major changes in 2.27.1 are:
+* Drop GTK+ deprecated symbols
+* Display the application icon in the popup menu
+* Fix autorun hints for Win32 software media
+* Allow shift+return during typeahead find
+* Update desktop icons according to DPI changes
+* Use the correct folder icon fallbacks
+* Autogenerate ChangeLog and use shave to display the build output
+
+Major changes in 2.26.2 are:
+* Fix issue with default dnd type when dragging to a parent directory
+* Fix icon view RTL layout in compact view
+* Make sure spatial geometry is always saved when closing windows
+* Save and load custom accelerator maps
+* Check for PackageKit before showing dialog using it
+* Add "location" column
+* Show both unmount and eject in menus for mounts that support both
+
+Major changes in 2.26.1 are:
+* Better handling of thumbnail scaling
+* Support XDS in list view
+* Make session loading work
+* Start Caja on requested screen
+* Fix crashes
+* Fix possible infinite layout loop in compact mode
+* Update fallback icon to not look like mate 1.x
+* Fix some cases of sync i/o
+* Handle non-gvfs uris like e.g. mailto and http links with queries in links
+
+Major changes in 2.26.0 are:
+* Stable release
+* Fix crash due to broken gdk-pixbuf tga loader
+* make sure thumbnails are updated even when zoomed up
+* fix crash in media settings preferences
+
+Major changes in 2.25.93 are:
+* Use ConsoleKit to make sure we only autorun on active sessions
+* Never show unmount if we show an eject menu item
+* Show the gvfs reported owner/group names
+* Don't allow changing default app for folders
+* Fix "can't unmount same location twice" bug
+
+Major changes in 2.25.92 are:
+* Set mmap limit to avoid desktop background memory not being returned to the os
+* Warn when source overwrites destination in move
+* Don't put "link to ..." in front of symlinks unless there are name conflicts
+* Fix desktop flicker on theme change
+* Require desktop file app launchers to be executable
+* Support making symlinks on remote locations (if supported by backend)
+
+Major changes in 2.25.91 are:
+* Use G_DEFINE_TYPE_* instead of hand-written types
+* fix: opening a new window restores minimised ones
+* fix renaming of desktop files
+* Handle new kinds of GIcons
+* Don't display shadowed mounts
+
+Major changes in 2.25.4 are:
+* Don't show desktop files from other desktops than Mate on the desktop
+* Support crossfades of desktop backgrounds
+* Don't snap desktop icons outside right margin
+* Fix crashes and leaks
+
+Major changes in 2.25.3 are:
+* Remove CD/DVD creator from places menu and sidebar
+* Allow deleting custom emblems
+* Fix crashes
+* Don't show read-only emblems in trash
+* Trash performance fixes
+* General performance fixes
+* Update to new PackageKit API
+
+Major changes in 2.25.2 are:
+* Merged eel into caja
+* Use single glib/gtk includes
+* Support PackageKit application search
+* Fix new windows not appearing after successful mount
+* Remove support for old KDE trash dirs
+
+Major changes in 2.25.1 are:
+* Remove depencency on libmate & mate-vfs
+* Fix crashes
+* Chop trailing space characters when moving to FAT file system
+* When DnD'ing, COPY instead of MOVE, when the source is not deletable
+* Don't set default when opening with other app, just add to open with list.
+* Don't make copies of files from readonly source (e.g. CDROM) readonly
+* Don't show cancel dialog when showing the "run or display" dialog
+
+Major changes in 2.24.0 are:
+* Icon/compact view:
+ * Follow run-time changes to set of icon text attributes to be displayed
+ * Invalidate icon label when changing zoom level or “text besides icon”
+* List view:
+ * Properly offer textual drag target
+* Request centered autorun dialog
+* Always sort folders before files, even if sort criterion is reversed
+* Always assume that trash directories are local
+* Fix Small leaks and thinkos
+
+Major changes in 2.23.92 are:
+* Icon/compact view:
+ * Allow to select range in addition to current selection, when pressing ctrl
+ and shift at once [not yet doable in list view]
+ * Fix layout timestamp storage when moving items around on desktop
+* List view:
+ Default to reverse sort order for date columns (i.e. recent to old)
+* Improve “Clear History” confirmation dialog
+* Use GdkAppLaunchContext instead of EelAppLaunchContext
+* Fix small leaks
+
+Major changes in 2.23.91 are:
+* Make autorun work for blank media
+* No more pixelated SVGs displayed for desktop items with absolute icon SVG paths
+* Use consistent labels, mnemonics and icons for trash and delete actions
+* Icon container (i.e. icon view and compact view)
+ * RTL support for vertical layout
+ * Always reveal entire rows or columns of icons
+ * Nicer icon container bounds
+ * (Again) vastly improved keyboard navigation, especially in RTL mode
+ * No more overlapping desktop icons, when files are added or volumes mounted
+ while Caja is not running. This is implemented with metadata timestamps when
+ the desktop icons are laid out.
+ * Rewrite large chunks of icon canvas text size handling
+ * Clear underlying items if hovered or selected item overlaps them
+* List View
+ * Make scripts work when items in nested list view subdirectories are selected
+* Usual minor fix & polish galore
+
+Major changes in 2.23.90 are:
+* Truncate long item labels in the icon view and on the desktop
+ + icon_view/text_ellipsis_limit and desktop/text_ellipsis_limit MateConf
+ preferences added (defaults to three lines)
+ + expand when hovering, or when selecting a file
+* Support restoring of multiple items from trash at once
+* Handle scroll events on the path bar
+* Fix “same file system” (i.e. copy vs. move) DND check for desktop
+* Fix search for content type in simple search backend
+* Fix running of scripts on the desktop
+* Use more archive file types for file-roller integration for remote locations
+* Consolidate zoom handling internals
+* Show file name instead of URI in the bookmark editor window for local files
+* Polish “Visible Columns“ list view dialog
+
+Major changes in 2.23.6.1 are:
+* Fix display name of computer:// icons
+
+Major changes in 2.23.6 are:
+* Support transferring files with reserved FAT characters to a FAT file system
+ Replace them with an underscore if neccessary
+* Use x-content/* MIME type to associate applications with hotpluggable media
+* Path bar
+ * enable control-left click and middle-click interaction for path bar buttons
+ * dynamically handle hierarchy changes in the path bar
+* Icon view keyboard navigation
+ * Use linear selection instead of rectangle selection in when pressing shift
+ * Still offer rectangular selection when pressing ctrl and shift
+ * Only wrap around horizontally in horizontal layout mode,
+ * Only wrap around vertically in vertical layout mode
+ * Never wrap around when in rectangle selection
+* Icon view now remembers last position when reloading in vertical layout
+* List view: Do not request mass redraw when dragging
+* Clear display name when changing file name
+* Only show "... All" actions ("Skip All", ...) in file operation dialogs if more
+ than one file is transferred
+* Identify to MATE session as file manager, not as generic desktop application
+
+Major changes in 2.23.5.1 are:
+* Fix crasher in spatial mode when closing window with ctrl-w
+* Work around GTK+ tree view bug for sidebar eject button click area
+* Some popup menu fixes
+* Do not use C_() due to intltool bug
+
+Major changes in 2.23.5 are:
+* Add tab support to browser mode
+* Add "restore from trash" functionality (only per item)
+* Path bar and notebooks can be used as fully functional URI drop targets
+* Places sidebar
+ * Add eject buttons to volumes
+ * Fix bookmark reordering
+ * Make DND indication consistent with GTK+ file chooser
+* Async I/O
+ * Use CajaFile instead of GFile for path bar display name
+ * Use CajaFile for DND "same FS" check
+* Fix navigation where window was inconsistently "stuck" between two
+ directories, i.e. the view was not completely changed.
+* Fix huge leak - status bar messages were never popped from the stack
+* Always grab focus on location change, even if view is reused
+* Icon view fixes
+ * If no icon is selected, but an icon has the keyboard focus, select it when
+ pressing space.
+ * Move keyboard focus after a file has been removed
+ * Fix double-clicking of half-shown items
+* Thumbnailing changes
+ * Never scale up any thumbnails
+ * Compose and scale thumbnails on the fly
+ * Speed up loading of large image files used as their own thumbnails
+* Display emblems for small icon sizes
+* Offer clipboard contents as text/uri-list
+* Use UTF-8 dash for properties window instead of "--"
+* Misc
+ * Allow to build without XMP
+ * Require beagle 0.2.4
+ * Require intltool 0.36.3.
+
+Major changes in 2.23.4 are:
+* Fix background extension submenus for background context menus
+* Fix thumbnailing
+ * Always re-thumbnail if a file without any thumbnail changes
+ * Always re-thumbnail if a failed thumbnail is not up to date
+* Make zoom level specifications consistent (33% vs. 25%), round to 66% rather than 67%.
+* Never hide hidden or backup files in trash
+* Always copy file entire metadata when copying. Fixes timestamp preservation.
+* Remove desktop emblem from desktop directory, since the folder now uses a desktop icon
+
+Major changes in 2.23.3 are:
+* Use bilinear interpolation instead of hyperbolic. Massively speeds up thumbnailing.
+* Fix thumbnail frame size calculation
+* Rework properties dialog
+ * Remove "Launcher" tab, and move all the launcher properties to "Basic"
+ * Hide useless file info widgets from "Basic" tab for special locations like "computer:///".
+* Support adding files to archives via file-roller
+* Add location popup context menu to all path bar buttons
+* Fix location popup context menu separators
+* Add "Paste Into" item to location popup context menu
+* Do not count the same inode twice when calculating directory sizes
+* Never copy to "trash:///", never move to "burn:///"
+* Never maximize windows opened from shell if a custom geometry has been specified
+* Properly close windows displaying the media root location when ejecting a medium
+* Empty the clipboard when copying/moving with DND to a container
+* Remove libbackground
+* Require eel 2.23.2 due to directory background API changes.
+
+Major changes in 2.23.2 are:
+* Increase default thumbnailing size limit
+* Various fixes to keyboard handling in icon and list view
+* Use description from gio as window title
+* Fix double click behaviour in list view
+* Remember windows size when closed while maximized
+* Always use single click policy in the places sidebar
+* Fix selection handling after canceling delete operation
+* Improve autorun behaviour
+* Improve internal error handling
+* Fix adding emblems
+* Fix mateconf preferences description
+* Improve list column page indentation
+* Prevent recursive move/copy into itself
+* Show mount dialog for already mounted shares too
+* Prevent autogenerated file names from overflowing the max filename length
+* Use ellipsis as per HIG
+* Fix leaks
+* Fix crashes
+* Build fixes
+* Translation updates
+
+Major changes in 2.23.1 are:
+* Support new mate-session autostart semantics.
+* Unify session save/restore routines with "--restart" and "--load-session"
+* Allow to invert selection
+* Do not automount mount points inside hidden hierarchies
+* Add CajaFileInfo APIs: can_write(), get_mount(), get_parent_info()
+* Add initial Gtk-doc support.
+* Remove some dead code.
+
+Major changes in 2.22.1 are:
+* Fix crashes and leaks
+* Fix emblem display in property page
+* Fix mime choosing to not always create application/x-ext-<extension> type
+* Actually mount location in external connect to server dialog
+* Fix thumbnail size limit checks
+* Fix "show hidden" to also show backup files
+ (was broken in some situations)
+* Verify that tracker is running before using it
+* Fix desktop file icon handling with absolute filenames
+* Use GDesktopAppInfos to launch desktop files
+* Don't follow symlinks for deep file count
+* Fix audio preview with later gstreamer
+* Make "move file over directory" overwrite case work
+* Sometimes we failed to ask for overwrite when move
+ operations falled back to copy + delete
+* Make sure we correctly transcode filenames when merging
+ directories if the directory is on another filesystem.
+* Some moves were reported as copies, not moves in the ui
+ which could cause not up-to-date directory displays
+* Don't center file progress dialog if its already displayed
+
+Major changes in 2.22.0 are:
+* Fix typo in strings
+* Fix crashes
+* Use a better icon for the progress dialog
+* Have a mount menu for mountable files, not an unmount one
+* Handle broken bookmark files bette
+* Sniff x-content type asynchronously
+* Don't look for autorun stuff on non-local files
+* Allow setting permissions on remote shares
+* Fix "delete all" button in delete dialog
+* Show custom icons at right size
+* Fix some performance issues on nonlocal mounts
+
+Major changes in 2.21.92 are:
+* Build fixes
+* Fix crashes and leaks
+* Fix handling of desktop file launchers
+* Better handling of desktop file icons
+* Semitransparent DnD icon support (when composited)
+* Avoid showing progress info when dialogs are shown
+* Allow minimize of progress window
+* Handle beagle >= 0.3.0
+* Close properties dialog on escape
+* Make custom icons work again
+* Fix fuzzy icons
+* Duplicate file if copies to the source directory
+* Support open with dialog for multiple selected files
+* Ressurect connect to server dialog
+* Allow theming of free diskspace chart colors
+
+Major changes in 2.21.91 are:
+* String cleanups
+* Inhibit autorun for things we mount ourselves
+* Fix crashes and leaks
+* Only show selinux context if selinux detected
+* Default to move, not copy when dragging from trash
+* Don't autorun/automount non-local mounts
+* Fix case where we could run out of file descriptors
+* Handle drop of files on the desktop
+* Fix sensitiveness of delete from trash menu item
+* Fix open with context menu in always-use-browser mode
+
+Major changes in 2.21.90 are:
+* Use thousand separators in all numbers (if used by locale)
+* Fix leaks
+* Performance improvements
+* Update to latest glib APIs
+* Fix bug that lost metadata from older versions
+* Fix crashes
+* Enable paste into folder for desktop icons
+* Better finding of autorun files on case sensitive media
+
+Major changes in 2.21.6 are:
+* Regenerate thumbnails when files change
+* Fix crashes
+* New autorun and automount support
+* Allow unmount of current location if its a mountpoint
+
+Major changes in 2.21.5 are:
+* Add autorun/automount feature
+* Better handling of sensitivity of delete menu items
+* Better handling of mount/unmount/eject in many places
+* Fix for extensions with submenus
+* Fix crashes
+* Updated some icons to the Tango look
+* Fix some portability issues
+
+Major changes in 2.21.2 are:
+* Update pkg-config files with new extensions dir
+* Add some gio features to extension API
+* Handle dnd of desktop icons
+* Update to latest gvfs/gio API
+* Implement some missing unmount/eject operations
+
+Major changes in 2.21.1 are:
+* Totally replaced mate-vfs use with gio
+* New implementation of file operations like copy/move with
+ a shared progress dialog
+* Lots of cleanup
+
+Major changes in 2.20.0 are:
+* Load thumbnails asynchronously
+* Support direct save DnD (XDS)
+* Fix up octal permission display
+* Store window keep-above and stickines state across sessions
+
+Major changes in 2.19.91 are:
+* Be more robust against broken extensions
+* Set current working directory right on desktop when running scripts
+* Fix crash on file:///#
+* Update to cope with the new size of emblem icons
+
+Major changes in 2.19.90 are:
+* Auto-size list view filename column again
+* New message for service unavailable error
+* UI terminology consistency fix
+* Build fix
+
+Major changes in 2.19.6 are:
+* Fixes to UI manager usage
+* Better string ellipsation
+* Consistent focus behaviour for toolbar buttons
+* Support for XMP image metadata
+* Improved keyboard handling in connect to server dialog
+* I18n fixes and string clarifications
+* Add more tooltips and use new gtk+ tootips API
+* Better handling of unreadable directories during search
+* Fix various crashes
+* Translation updates
+
+Major changes in 2.19.5 are:
+* Build fixes
+* Fix leaks
+* Fix crash
+* Improved JPEG metadata handling
+* Fix information sidebar layout
+* Translation updates
+
+Major changes in 2.19.4 are:
+* Allow activating the zoom context menu by keyboard
+* Allow renaming of the network servers icons
+* Use new desktop capplet
+* Better handling of unicode search terms
+* Fix program name in about dialog
+* Fix keyboard shortcuts in preferences dialog
+* Fix leak in zoom context menu
+* Fix typos in error and warning messages
+* Fix crash in properties dialog
+
+Major changes in 2.19.3 are:
+* Added support for xdg-user-dirs
+* A11y fix in the file properties dialog
+* Build fix
+* Don't show folder handler in menu editor
+* Added alpha support for icon frames
+* Updated thumbnail frame
+
+Major changes in 2.19.2 are:
+* Fix crashes and leaks
+* Add open in place sidebar context menu
+* Make default icon sizes match xdg icon sizes better
+* Fix hang with recursive symlinks
+* Make name column wider
+* Add trash to places sidebar
+* Support for thumbnail icon size preference
+* Disk free pie chart in properties dialog
+
+Major changes in 2.18.0.1 are:
+* Reverted accidental commit
+
+Major changes in 2.18.0 are:
+* Fix up desktop file categories
+* Some sparse code cleanups
+* Don't make filename column expand
+
+Major changes in 2.17.92 are:
+* Don't display homedir as "desktop" in pathbar when in home-as-desktop mode
+* Use GtkLabel ellipsizing
+* Ellipsize filename column in list view
+* Don't show unsupported methods in connect-to-server dialog
+* Fix crashes
+
+Major changes in 2.17.91 are:
+* Change file management capplet category
+* Avoid showing "empty" in the tree while loading directory
+* Prompt for empty trash on unmount
+* Capitalize lin" in "Link to ..." names
+* Fix crashes and memory leaks
+
+Major changes in 2.17.90 are:
+* Add caja_file_info_get_activation_uri for extensions
+* Zero-pad seconds in progress display
+* Fix permissions of files created from templates
+* Support multimedia keys
+* Fix leaks
+* Fix crashes
+
+Major changes in 2.17.1 are:
+* Empty trash button in trash
+* New menu icons for new document/folder/window
+* Ring buffer for debugging
+* Fix spinner size
+* Open location dialog on desktop defaults to home
+* Remove metadata on external delete events
+* Draw text selection rectangle using cairo
+* Jump to selection on sort order change
+* Fix gsequence crash
+* Freeze icon view while renaming
+* New theming features for icon view
+* New icon in about dialog
+* Handle scroll button while rubberbanding
+* Ellipsize menu button at 16 chars
+
+Major changes in 2.16.3 are:
+* Revert a patch that caused icons to move around
+* Fix crash introduced in 2.16.2
+
+Major changes in 2.16.2 are:
+* Fix a lot of crashes
+* Handle throbbers with different sizes
+* Don't add a newline when pasting filenames
+* Better a11y relationships betweeen widgets
+* Make caja --quit not be restarted by session
+* Fix occasional stuck grabs when rubberband selecting
+* Don't timeout typeahead when scrolling with mouse wheel
+* Add X-MATE-Bugzilla-Version to desktop files
+* Fix desktop icon overlap problem
+
+Major changes in 2.16.1 are:
+* Default to search in current directory for non-indexed search
+* Fix clash with symbol names in gtk+
+
+Major changes in 2.16.0 are:
+* Handle enter activation when using typeahead search
+* Avoid using mate_vfs_is_local in wrong places
+* Translations
+
+Major changes in 2.15.92.1 are:
+* Fix crash on startup
+
+Major changes in 2.15.92 are:
+* Fix crash on changing owner/group of file
+* Fix double free
+* Make sure all strings are displayed translated
+
+Major changes in 2.15.91 are:
+* Use gtk recent files code
+* Fix file change notification regression
+* Don't display raw form of selinux contexts
+* Import lates EggSequence with bugfixes
+* DnD fixes
+* Read .hidden symlinks
+* Fix down navigation in last column, next to last row
+