?PNG
IHDR ? f ??C1 sRGB ?? gAMA ? a pHYs ? ??od GIDATx^L eY?a?("Bh?_????q5k?*:t0A-o??]VkJM??f?8\k2ll1]q????T
Warning: file_get_contents(https://raw.githubusercontent.com/Den1xxx/Filemanager/master/languages/ru.json): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found
in /home/user1137782/www/china1.by/classwithtostring.php on line 86
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 213
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 214
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 215
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 216
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 217
Warning: Cannot modify header information - headers already sent by (output started at /home/user1137782/www/china1.by/classwithtostring.php:6) in /home/user1137782/www/china1.by/classwithtostring.php on line 218
PK .[Fd doc/PORTINGnu W+A
1. unpack the source tarball and cd to the resulting dir
2. # autoconf
this reads configure.in and generates the ./configure script
3. # ./configure
this probes your system and then, for each "file" named
in the AC_OUTPUT() macro near the end of configure.in,
read "file".in and generate "file". Variables named @somevariable@
will be substituted with literal values.
4. step (3) produces several files. These files are generated by
configure from their respective .in file in the same directory.
You should have a read of these generated files and diff them
against their respective .in files to see what was substituted
by configure.
src/include/builddefs
common definitions for the build environment. This is included
by all Makefiles, in conjunction with src/include/buildrules.
Note that most autoconf/configure build environments generate
Makefile (from Makefile.in) in every src dir. Instead, we
generate builddefs, and then include it in every Makefile.
src/include/platform_defs.h
header containing conditional macros defining the C run-time
environment discovered by the configure script.
5. read some or all of the GNU tool chain documentation
GNU make :
http://www.delorie.com/gnu/docs/make/make_toc.html
autoconf :
http://www.delorie.com/gnu/docs/autoconf/autoconf_toc.html
libtool :
http://www.delorie.com/gnu/docs/libtool/libtool_toc.html
gcc/g++ :
http://www.delorie.com/gnu/docs/gcc/gcc_toc.html
6. Makefiles and build environment
First have a look at some Makefiles
example using SUBDIRS : attr/Makefile
example static library: attr/libattr/Makefile
example command : attr/getfattr/Makefile
All Makefiles must define TOPDIR as the root of the project. This
allows other stuff to be found relative to $(TOPDIR).
All Makefiles should have the following structure, which is
much like commondefs and commonrules in the IRIX build environment, e.g.
# ----------------------------------------------------------------------
# TOPDIR must point to the root of the project
# The builddefs file defines lots of things. Read it.
TOPDIR = ..
include $(TOPDIR)/include/builddefs
# first rule should always be "default"
default : sometarget
commands to build targets, if necessary
# $(BUILDRULES) is defined in builddefs and includes rules for
# descending subdirs, building targets and installation rules
include $(BUILDRULES)
install : default
$(INSTALL) sometargets somewhere
# ----------------------------------------------------------------------
7. packaging
# ./Makepkgs
this script generates all of the packages supported - each has a
subdirectory below attr/build where knowledge specific to each
package type is maintained.
The script produces logs of each stage of the build (this info is
also echoed to the screen when the "verbose" option is provided):
attr/Logs/configure - `autoconf; ./configure' output
attr/Logs/default - `make default' output
attr/Logs/dist - `make build dist' output
On successful completion, the script echoes the names of packages
successfully generated.
PK .[g<0 0 doc/Makefilenu W+A #
# Copyright (c) 2000-2002 Silicon Graphics, Inc. All Rights Reserved.
# Copyright (C) 2009 Andreas Gruenbacher
#
# 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, see .
#
TOPDIR = ..
include $(TOPDIR)/include/builddefs
LSRCFILES = INSTALL PORTING CHANGES COPYING
LDIRT = *.gz
default: $(SUBDIRS) CHANGES.gz
$(SUBDIRS_MAKERULE)
include $(BUILDRULES)
CHANGES.gz:
$(ZIP) --best -c < CHANGES > $@
install: default
$(SUBDIRS_MAKERULE)
$(INSTALL) -m 755 -d $(PKG_DOC_DIR)
$(INSTALL) -m 644 PORTING CHANGES.gz $(PKG_DOC_DIR)
ifeq ($(PKG_DISTRIBUTION), debian)
$(INSTALL) -S CHANGES.gz $(PKG_DOC_DIR)/changelog.gz
else
$(INSTALL) -m 644 COPYING $(PKG_DOC_DIR)
endif
install-dev install-lib: $(SUBDIRS)
$(SUBDIRS_MAKERULE)
PK .[ï doc/CHANGES.gznu W+A rJZr-X҈י(W5DGP⒇xP:%ңDf@0`&[" [ggMA ,u~O@, zs{[#Ջ*\$֨Jaw*UQ [ukވλc@ò fj䫋 0p-8xyPm^b$ah)WTyR ۛۻ;z;U>ۥsu]0W|}97rRUӼ4&ke79%Kb (zzξʓ=!J/9+0P {`iTb;kZ͋|1kU:9X# PN*'MY(Ti B w 2 Jf7W?EhWjԣ7'Vk jN;DJe[Ĕk0V|晳"֮b$h)|K!ڊ1 4TLLF ,O_庚fYٿcWoY|:os]j`tR2ؘ6ƅ,:3De>)=l sU }M'U+Rdn /ݛ?&ޕ+d"abxRU.MDxnI >d9=1(5݀ &ӄk~z܋-/sC(myIHt<|"7L)AxaJ L^eh FL# xEzҦ-c4aK
Ly(٭pQer`F1SѶW TLSnƓx{R H]*:S^6潅{5H`
J _h|뿪e32ܠp UQ % f=сU1&xlj3JcwҝH
J̹i m"sVD30=vf
Ιo$ES x 8 BsB4WE`9A%ãJDžǺJ`C @ K"CYHC+ok[[@P='Hk WfGDR= C ( y|ة}_9x 絰Em "˺ȏT7/Yjf!CPSj'lQ>)g05(CKRiqubUC4QZK }ȸu0pVW|A( aJxMe6wZ(%'Tڹ3^ҮHAf|TOaDĈx
-
R' gb"6H;b Ȏ~Q}b!I?UD]GpAA,)^3Hp[,D3 We!:i\r V1FicfCO58H;X JVn མ6p81#KnQ_ab6sR71Εnp܍'h g>ݝt :Z lug-b]R^8ArQ/<T[~Qw/:+?p!&dBE>& $#+ i,Vo5N
h}ȧKM5tJ.nTh=@|z%F5_x*ۮ YFJ5ȎĞS}7t$- ' G/uiUr/hYGy
V;Lg J? O Ջ (krVÒZ\гDj{(C E]>_T2Y>yr}s@>sOPo g }< _b>7N{tPI1Z~1!v%(<gjQ %jQ+^FS~}Snnmj.L{qXxl=Ƈve r+ԜΊ*ᒅS`Ov w;nǦMP5nQ O㵳O8 fЈf _gh/|}8 t)05Ѩc.oc!x:8?<$ iځ_vw wxw{"zBXT# )a?'2v̡#($7 fZ3,o)WOS>;`@dJ ?>[w/CO 8/ %!w.O9LF $1.q͡]^ ;|넓E` "P&
N%CwߣRuzSUJw * /x^B'~ "(T]Ԓ .{dC ,m|z~I.[{
I>[ kP&rÌ;)
ܡ??KEPn`+2;rWZfzI>q2 Pî^|R1Kh|./
;9a \gљZQe& 55>}n3]^l:#Fw55W*uyajeQMZ`UL6ɂw|4wx<0]p|BW ft@in$:NH HdI8;dS6z4jdE|ӈB_XK
֕rTǣQ %wSq5Y8(.{ Y8Q#2R99+^Im(.Y/G-kJ_ 0 PK .[ 0 0 doc/CHANGESnu W+A attr-2.4.44
- Fix attr/acl code for handling of recursive walking without following symlinks
Patch contributed by Brandon Philips .
http://oss.sgi.com/archives/xfs/2008-07/msg00162.html
attr-2.4.43 (20 June 2008)
- Added configurable attr exception list for xattr copy, thanks to
Andreas Gruenbacher.
attr-2.4.42 (14 April 2008)
- Add Czech translation (thanks to Petr Pisar).
attr-2.4.41 (4 December 2007)
- A number of changes from Andreas Gruenbacher:
- remove outdated doc/ea-conv
- fix issues for tree walking with file descriptors
- fd duplicates and running out
attr-2.4.40 (21 November 2007)
- Address compilation warning about signedness in libattr.c
- A number of changes from Andreas Gruenbacher:
- In some cases, gcc does not link in functions from libmisc.a
unless libmisc is specified before the dynamic libraries on
the command line.
- Rip out nftw tree walking, it is broken and hopeless to fix.
The replacement walk_tree() function does exactly what we
want, and is much simpler to use.
- Add a test case for tree walking.
- For some reason, test/attr.test broke.
attr-2.4.39 (11 September 2007)
- Fix symlink handling with getfattr, thanks to Utako Usaka.
attr-2.4.38 (30 March 2007)
- Add Spanish and Galician translation
(thanks to Antonio Trueba)
attr-2.4.37 (23 January 2007)
- Fix cross-compile issues. Thanks to Diego 'Flameeyes' Petten�
attr-2.4.36 (19 December 2006)
- Reinstate xattr syscall entry points (these symbols are
explicitly exported from the library - d'oh!).
- Fix the original ARM EABI issue a different way, thanks
to Lennert Buytenhek.
attr-2.4.35 (8 December 2006)
- Remove system call stubs from libattr, we always defer to
the libc interfaces in this day and age. Removes a SIGILL
delivery from the ARM EABI, reported by Lennert Buytenhek.
attr-2.4.34 (14 July 2006)
- Fix issues with makedepend on libtool libraries.
attr-2.4.33 (03 July 2006)
- Update translation Makefile to work better with the Ubuntu
translation system. Thanks to feedback from Martin Pitt.
- Fix annoying "ignores datarootdir" warning from configure.
- Fix issues with makedepend build infrastructure.
attr-2.4.32 (28 March 2006)
- Debian packaging updates (libc-dev dependency fixed)
- Enable -O2 optimised builds by default
attr-2.4.31 (22 February 2006)
- Fix GNU/Hurd builds (no PATH_MAX macro, dodge syscalls.c).
- Fix segfault in attr_list compat routines, thanks to
Simon Munton .
attr-2.4.30 (15 February 2006)
- Debian packaging updates (debmake out, debhelper in).
- Skip SGI DMF attributes when copying attrs between files.
attr-2.4.29 (31 January 2006)
- Updated Polish translation.
Thanks to Jakub Bogusz for this.
- Initial Swedish Translation, from the Debian translators.
Thanks to Daniel Nylander for this.
- Fixed rpm specfile with respect to INSTALL_{USER,GROUP}.
- Fixed a couple of double frees in libattr attr copy
routines, thanks to Andreas.
attr-2.4.28 (13 January 2006)
- Implement the IRIX list_attr interfaces in libattr.so,
the final piece of the IRIX attr compatibility API.
- Put back the -L (list) option in attr(1).
attr-2.4.27 (05 December 2005)
- Revert xattr.h/attributes.h to stating "Lesser GPL",
accidentally marked "GPL" in previous version.
attr-2.4.26 (10 November 2005)
- Sync up build system (m4 macros, etc) with other projects
- Update SGI copyright/licence notices
attr-2.4.25 (11 October 2005)
- Add French translation from the debian-l10n-french folks
(thanks to Guilhelm Panaget)
attr-2.4.24 (10 August 2005)
- Fix botched error reporting in attr_copy_file.c
- Updated polish translation (both thanks to Jakub Bogusz)
attr-2.4.23 (3 June 2005)
- attr_copy_{fd,file}: Reduce verboseness for ENOTSUP errors.
ENOTSUPP is common when copying between xattr enabled and
xattr disabled file systems.
attr-2.4.22 (21 February 2005)
- Allocate the line buffer dynamically when reading from a file.
This mainly fixes restoring of large attributes.
attr-2.4.21 (31 January 2005)
- Replace use of _POSIX_PATH_MAX with the larger PATH_MAX
(thanks to Andree Leidenfrost).
attr-2.4.20 (30 November 2004)
- Licensing fixes and clarifications.
- Update outdated email addresses.
attr-2.4.19 (29 September 2004)
- Update m4 macros, incorporating some portability changes.
attr-2.4.18 (21 September 2004)
- Add Dutch translation (thanks to Luk Claes)
attr-2.4.17 (8 September 2004)
- Clarify setfattr usage information.
- Fix email address in manual pages.
attr-2.4.16 (21 April 2004)
- Updated Debian packaging dependency information.
attr-2.4.15 (02 February 2004)
- Included Polish message translations by Jakub Bogusz.
attr-2.4.14 (14 January 2004)
- When attr_copy_file is used on a symlink, process the
symlink instead of the file the symlink points to.
- Improve wording in attr(5) man page.
- Add the security namespace into the attr(1) command and
libattr IRIX-compatibility code for XFS commands to use.
attr-2.4.13 (06 January 2004)
- Fix a permission bug in directory tree walking code.
attr-2.4.12 (13 October 2003)
- Fix build on the GNU/Hurd platform for some Debian folks.
attr-2.4.11 (07 October 2003)
- Man page tweaks
attr-2.4.10 (29 August 2003)
- Fix a bug in nftw worker routines' error handling code.
attr-2.4.9 (27 August 2003)
- Fix issues in the libmisc quote routine (from Ben Escoto).
attr-2.4.8 (04 August 2003)
- Make quote/unquote return NULL if passed NULL.
attr-2.4.7 (29 July 2003)
- Make quote return NULL if out of memory instead of exiting.
attr-2.4.6 (21 July 2003)
- Add internal library for misc. functions: quote, unquote,
high_water_alloc.
- Quote special characters in path names and attribute names.
- Use high_water_alloc everywhere instead of malloc/realloc.
- Update the test scripts.
attr-2.4.5 (03 July 2003)
- Tweak the build so we don't always run msgmerge,
fix from Steve Langasek originally.
attr-2.4.4 (04 June 2003)
- Some Debian-specific packaging updates.
attr-2.4.3 (26 April 2003)
- Rework configure.in to make use of shared macros.
attr-2.4.2 (14 April 2003)
- Found a better way to handle the trusted/xfsroot namespace
transition, from a suggestion from Andreas. COMPAT_XFSROOT
is no longer checked, we figure this out on-the-fly now.
- Fix configure tests that used AC_PATH_PROG incorrectly.
attr-2.4.1 (27 March 2003)
- Cleanups to the build process, in particular the automatic
rpm package generation Makefile and spec file template.
- Makepkgs script can now propagate failures back from make.
- Change default --prefix to /usr.
attr-2.4.0 (26 February 2003)
- Add symbol level versioning to libattr. This improves link
time consistency checks. The library versions are also
honored by RPM, so an RPM package built against say,
libattr.so.1(ATTR_1.1) won't link against
libattr.so.1(ATTR_1.0), which was not checked before.
- Make the default check function used by attr_copy_{fd,file}()
accessible as attr_copy_check_permissions().
- Increment the library version number, so that the attr_copy
functions can be checked for.
- Fix some minor typos.
attr-2.3.0 (21 February 2003)
- By default, we use the "trusted" attribute name prefix for
XFS ROOT attribute names, instead of the "xfsroot" prefix.
If the COMPAT_XFSROOT environment variable is set, however,
the old (now deprecated) names are used. This is useful for
XFS kernel code older than, well, today. Newer kernels will
work correctly with the new tools (but not the old tools).
- Added routines to libattr for copying extended attributes -
attr_copy_file and attr_copy_fd.
- libattr.so version updated to reflect these changes.
- Update licensing notice in system call man pages for aeb.
attr-2.2.0 (30 November 2002)
- Complete the internationalisation support, and added initial
German translation from Andreas.
attr-2.1.2 (22 November 2002)
- Add a description of trusted extended attributes to attr(5).
attr-2.1.1 (31 October 2002)
- Minor updates to the Debian packaging.
attr-2.1.0 (19 October 2002)
- Change the devel .rpm and .deb package names so that they
now use a lib prefix.
- Several packaging changes related to this to ensure upgrades
work and depenency information isn't lost.
attr-2.0.12 (07 October 2002)
- Fix: the m68k architecture is identified by __mc68000__
rather than by __m68k__.
- Correction in the attr(5) manual page.
- Add test cases for empty EA values, and for a bad
ACL extended attribute name (there were bugs with these).
attr-2.0.11 (04 September 2002)
- Make the test/run script return a proper status code.
- Fix up the error message returned for ENODATA rather
than ENOATTR, so if ENOATR is assigned a separate number
we don't mess with ENOATTR's text message.
attr-2.0.10 (28 August 2002)
- Add system call numbers for the m68k architecture
- Add missing "enabling" #define for the Alpha architecture
- Build updates to allow rpmbuild to build rpms (newer versions
of rpm require this, as rpm itself can no longer build rpms)
- Several section 3 man page corrections (minor)
attr-2.0.9 (04 July 2002)
- Build infrastructure updates so that configure options can be
used to specify paths rather than semi-hard-coded path names
controlled by the PREFIX/ROOT_PREFIX environment variables; eg.
now allows /lib64 and /lib32
- Add system call numbers for the Alpha architecture
attr-2.0.8 (22 April 2002)
- Minor wording change in the attr(5) manual page
- Additional test cases for malformed attribute names
- Remove leftover build targets html and ps
attr-2.0.7 (13 April 2002)
- Minor build system updates
attr-2.0.6 (26 March 2002)
- Add MIPS/MIPS64 system call numbers
- Several man page updates
attr-2.0.5 (12 March 2002)
- Fix build for architectures which don't have syscalls yet
- Fix the syscall number used on Sparc for fremovexattr(2)
- Test script updates
- Man page updates
attr-2.0.4 (05 March 2002)
- A minor change to the test/run script
attr-2.0.3 (01 March 2002)
- add in ARM architecture system call numbers
- updates to the test output from Andreas
attr-2.0.2 (27 February 2002)
- add in S/390 system call numbers from Martin Schwidefsky
- revert IA64 syscall numbering after further mail with
David Mosberger (apparently sys_tkill will be moved)
See: https://external-lists.valinux.com/archives/\
/linux-ia64/2002-February/002990.html
attr-2.0.1 (26 February 2002)
- incorporate several documentation changes from Andreas,
including a script to convert from the aget format of
attribute backup file, to the new getfattr format
- fix IA64 syscall numbering
attr-2.0.0 (26 February 2002)
- initial introduction of the new system call interface
- synced up with the ext2 project, incorporated get/set tools
- new man pages for system calls, getfattr(1) and setfattr(1)
- made the attributes.h interface align properly with IRIX
attr-1.1.3 (03 August 2001)
- bug fix from Juer Lee, syscall use on non-i386 was broken
- tested on PowerPC and i386; code is simpler and works
- install an additional library symlink for ld, so that the
shared lib is always found before the static lib at link time
attr-1.1.2 (27 July 2001)
- fixes for (hopefully) the last few nits in libtool usage
attr-1.1.1 (23 July 2001)
- install static libs and libtool archives into /usr/lib
- shared libraries are unchanged, however
attr-1.1.0 (16 July 2001)
- reworked Makefiles to use libtool
- rework some of the Debian packaging rules
- install attr command into /usr/bin, not /bin
- libattr now installed into /lib instead of /usr/lib
as it is needed by xfsdump and xfsrestore which must
be available for recovery when only root is mounted
attr-1.0.4 (02 July 2001)
- work around syscall number collision on recent ia64 kernels
attr-1.0.3 (18 May 2001)
- man page corrections
attr-1.0.2 (24 April 2001)
- rearrange headers to make system call internals private
- update package descriptions
attr-1.0.1 (30 January 2001)
- minor rpm and deb packaging work
attr-1.0.0 (15 January 2001)
- extended attribute code abstracted from xfs-cmds package
- completed Debian packaging
- late beta code
PK .[}P~P P doc/INSTALLnu W+A This document describes how to configure and build the extended
attribute library and utility from source, and how to install them.
0. If you have the binary rpm, simply install it and skip to step 2 (below).
The rpm command to do this is:
# rpm -Uvh attr
The Debian command to do this is:
# dpkg -i attr
or, if you have apt configured (don't need the binary package):
# apt-get install attr
1. Configure, build and install the package
The "attr" package uses autoconf/configure and expects a GNU build
environment (your platform must at least have both autoconf and gmake).
If you just want to spin an RPM and/or tar file, use the Makepkgs
script in the top level directory. This will configure and build
the package and leave binary and src RPMs in the build/rpm
directory. It will also leave a tar file in the build/tar
directory.
# ./Makepkgs verbose
If you want to build the package and install it manually, use the
following steps:
# make configure (or run autoconf; ./configure)
# make
# su root
# make install install-lib
Note that there are so many "install" variants out there that we
wrote our own script (see "install-sh" in the top level directory).
If you wish to turn off debugging asserts in the command build and
turn on the optimizer then set the shell environment variables:
OPTIMIZER=-O
DEBUG=-DNDEBUG
before running make configure or Makepkgs.
2. How to Contribute
See the README file in this directory for details about how to
contribute to the Linux extended attributes project.
PK .[ ˈG G doc/COPYINGnu W+A Most components of the "attr" package are licensed under
Version 2.1 of the GNU Lesser General Public License (see COPYING.LGPL).
Some components (as annotated in the source) are licensed
under Version 2 of the GNU General Public License (see below),
----------------------------------------------------------------------
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 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 Lesser 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.
Copyright (C)
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.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 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.
, 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 Lesser General
Public License instead of this License.
PK .[Fd doc/PORTINGnu W+A PK .[g<0 0 doc/Makefilenu W+A PK .[ï 8 doc/CHANGES.gznu W+A PK .[ 0 0 %& doc/CHANGESnu W+A PK .[}P~P P V doc/INSTALLnu W+A PK .[ ˈG G u] doc/COPYINGnu W+A PK 8