From ad9db91ffc82f6a3766ab1cc9e6797b6729fcee5 Mon Sep 17 00:00:00 2001 From: Boram Park Date: Tue, 21 Aug 2012 18:03:52 +0900 Subject: [PATCH 1/1] upload tizen2.0 source --- ChangeLog | 194 ++++++++++++++++++ INSTALL | 291 +++++++++++++++++++++++++++ autogen.sh | 0 configure.ac | 13 +- docbook.am | 105 ++++++++++ packaging/xorg-x11-proto-scrnsaver.spec | 45 +++++ packaging/xorg-x11-proto-scrnsaverproto.spec | 50 ----- specs/Makefile.am | 63 +----- specs/saver.xml | 162 ++++++++------- 9 files changed, 733 insertions(+), 190 deletions(-) mode change 100755 => 100644 ChangeLog create mode 100644 INSTALL mode change 100644 => 100755 autogen.sh mode change 100755 => 100644 configure.ac create mode 100644 docbook.am create mode 100644 packaging/xorg-x11-proto-scrnsaver.spec delete mode 100644 packaging/xorg-x11-proto-scrnsaverproto.spec mode change 100755 => 100644 specs/Makefile.am mode change 100755 => 100644 specs/saver.xml diff --git a/ChangeLog b/ChangeLog old mode 100755 new mode 100644 index d77c417..5b3a31a --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,197 @@ +commit c33f4368e85d976b112dda4a34ca254944cb354d +Author: Alan Coopersmith +Date: Thu Mar 22 20:49:20 2012 -0700 + + scrnsaverproto 1.2.2 + +commit 27cf3d03cdd502c1228e59ba560eab77d8393405 +Author: Matt Dew +Date: Sat Jan 14 22:21:00 2012 -0700 + + informaltable cleanup + + On certain tables, add top and bottom borders to table + header and a bottom border to the table. This matches + what those tables in the old pdfs looked like. + + the prevents tables from + splitting across pages. Useful for tiny tables. + + Converting the colwidth to a floating point, + IE, 1* -> 1.0* cleans up these build errors: + WARNING: table-layout="fixed" and column-width unspecified + => falling back to proportional-column-width(1) + + Signed-off-by: Matt Dew + +commit ffbc319b69b1e3502a9b14195e7fa94f2beee3b6 +Author: Matt Dew +Date: Sat Sep 24 20:07:44 2011 -0600 + + Fix id attributes, linkend and olinks + + #1 - fix the capitolization of the ID attriutes to match either the or <funcdef> string it goes with. + #2 - fix any <linkend>'s that were affected by #1 + #3 - any <function> in the docs that has an actual funcdef, will become an olink if external, xref if internal. + + Reviewed-by: Gaetan Nadon <memsize@videotron.ca> + +commit 4aa72b32c7707bd78fc8dd8e287e3030eeb85d05 +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Tue Sep 20 20:17:40 2011 -0400 + + specs: fix markup for single license dual holder + + Signed-off-by: Gaetan Nadon <memsize@videotron.ca> + +commit d9c42cb0ba35e1c5e5a36a8cbde81eb311350931 +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Mon Sep 12 11:04:11 2011 -0400 + + docs: use the &fullrelvers; entity to set X11 release information + + Signed-off-by: Gaetan Nadon <memsize@videotron.ca> + +commit 378e4e73352a6bc11589460fdb4e6ceead2e82dc +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Sun Sep 11 19:49:54 2011 -0400 + + docs: remove <productnumber> which is not used by default + + This element is not rendered by default on the title. A template + customization is required to display it. + X Window System does not have a product number. + + Signed-off-by: Gaetan Nadon <memsize@videotron.ca> + +commit feaac4aaccb25d79d29a6020e75fca5a9938bf8a +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Thu Sep 8 20:00:00 2011 -0400 + + docbook.am: embed css styles inside the HTML HEAD element + + Rather than referring to the external xorg.css stylesheet, embed the content + of the file in the html output produced. This is accomplished by using + version 1.10 of xorg-xhtml.xsl. + + This makes the whole html docs tree much more relocatable. + In addition, it eliminates xorg.css as a runtime file which makes + xorg-sgml-doctools a build time only package. + + Signed-off-by: Gaetan Nadon <memsize@videotron.ca> + +commit 25764e51ecdea56df02063ae3b9d625d41a1209d +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Wed Sep 7 10:31:04 2011 -0400 + + docbook.am: global maintenance update - entities, images and olinking + + Adding support in libX11 for html chunking caused a reorg of docbook.am + as well as the xorg-sgml-doctools masterdb for olinking. + The parameter img.src.path is added for pdf images. + A searchpath to the root builddir is added for local entities, if present. + + The docbook.am makefile hides all the details and is identical for + all 22 modules having DocBook documentation. It is included by a thin + Makefile.am which requires no docbook knowledge. + + Signed-off-by: Gaetan Nadon <memsize@videotron.ca> + +commit e80d85902dcd19edd9bdb5f574ca47d0811ac0aa +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Sun Jun 12 17:54:50 2011 -0400 + + Install xml versions of specs even if HAVE_XMLTO is false + + DocBook/XML input source is also a usefull output format that can be viewed + with an XML viewer or editor and by some O/S help system. + + Signed-off-by: Gaetan Nadon <memsize@videotron.ca> + +commit 8f407c9417ffe2c1e01b37e18c71469d2baee970 +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Sun Jun 5 16:27:37 2011 -0400 + + Install target dbs alongside generated documents + + This matches a change in xorg-sgml-docs whereby the masterdb will look for + the target dbs into the same location as the generated documents. + + The target dbs are now installed alongside the generated documents. + Previously they are installed in $prefix/sgml/X11/dbs alongside masterdb which + has the potential of installing outside the package prefix and cause + distcheck to fail when user does not have write permission in this package. + + Requires XORG_CHECK_SGML_DOCTOOLS(1.8) which was released 2011-06-11 + +commit 2408165cb190a10e2d899bdc259866cbf7a8e125 +Author: Matt Dew <marcoz@osource.org> +Date: Wed May 25 22:04:10 2011 -0600 + + add id attributes to funcsynopsis to allow other docs to olink to them. + + Signed-off-by: Matt Dew <marcoz@osource.org> + Reviewed-by: Alan Coopersmith <alan.coopersmith@oracle.com> + Reviewed-by: Gaetan Nadon <memsize@videotron.ca> + +commit 2cd4a9898644dde49a876eeb53037149c85a37f0 +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Sun Feb 27 15:06:18 2011 -0500 + + Documentation: add Docbook external references support + + When writing technical documentation, it is often necessary to cross + reference to other information. When that other information is not in the + current document, additional support is needed, namely <olink>. + + A new feature with version 1.7 of xorg-sgml-doctools adds references to + other documents within or outside this package. + + This patch adds technical support for this feature but does not change + the content of the documentation as seen by the end user. + + Each book or article must generate a database containing the href + of sections that can be referred to from another document. This database + is installed in DATAROOTDIR/sgml/X11/dbs. There is a requirement that + the value of DATAROOTDIR for xorg-sgml-doctools and for the package + documentation is the same. This forms a virtual document tree. + + This database is consulted by other documents while they are being generated + in order to fulfill the missing information for linking. + Refer to the xorg-sgml-doctools for further technical information. + + Co-authored-by: Matt Dew <marcoz@osource.org> + + Signed-off-by: Gaetan Nadon <memsize@videotron.ca> + +commit 9d7dc8242feae5690e7aef48a386555c04183e9f +Author: Alan Coopersmith <alan.coopersmith@oracle.com> +Date: Thu Dec 16 23:16:54 2010 -0800 + + specs: change othercredit tags to author tags + + Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com> + +commit d50038590f72f02bc95712d8a4c37654f6d05a64 +Author: Alan Coopersmith <alan.coopersmith@oracle.com> +Date: Thu Dec 16 23:15:19 2010 -0800 + + spec: Fix section titles/nesting + + Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com> + +commit f85ed94ac012675dff25afbd3161dbbd3f62882b +Author: Gaetan Nadon <memsize@videotron.ca> +Date: Tue Nov 9 15:19:09 2010 -0500 + + config: HTML file generation: use the installed copy of xorg.css + + Currenlty the xorg.css file is copied in each location + where a DocBook/XML file resides. This produces about + 70 copies in the $(docdir) install tree. + + Signed-off-by: Gaetan Nadon <memsize@videotron.ca> + commit b4899c5d6090efdf292f5686cc23ed90e3729e4b Author: Alan Coopersmith <alan.coopersmith@oracle.com> Date: Fri Oct 29 23:27:16 2010 -0700 diff --git a/INSTALL b/INSTALL new file mode 100644 index 0000000..8b82ade --- /dev/null +++ b/INSTALL @@ -0,0 +1,291 @@ +Installation Instructions +************************* + +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, +2006, 2007, 2008 Free Software Foundation, Inc. + + This file is free documentation; the Free Software Foundation gives +unlimited permission to copy, distribute and modify it. + +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. + + 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. + + 4. Type `make install' to install the programs and any data files and + documentation. + + 5. 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. + + 6. Often, you can also type `make uninstall' to remove the installed + files again. + +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 `..'. + + 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'. + + 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. + + 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'. + +Optional Features +================= + + 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. + +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" + +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" + +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. + diff --git a/autogen.sh b/autogen.sh old mode 100644 new mode 100755 diff --git a/configure.ac b/configure.ac old mode 100755 new mode 100644 index 9938216..6a70989 --- a/configure.ac +++ b/configure.ac @@ -1,18 +1,19 @@ AC_PREREQ([2.60]) -AC_INIT([ScrnSaverProto], [1.2.1], +AC_INIT([ScrnSaverProto], [1.2.2], [https://bugs.freedesktop.org/enter_bug.cgi?product=xorg]) AM_INIT_AUTOMAKE([foreign dist-bzip2]) AM_MAINTAINER_MODE -# Require xorg-macros minimum of 1.10 for HAVE_STYLESHEETS in XORG_CHECK_SGML_DOCTOOLS +# Require xorg-macros minimum of 1.12 for DocBook external references m4_ifndef([XORG_MACROS_VERSION], - [m4_fatal([must install xorg-macros 1.10 or later before running autoconf/autogen])]) -XORG_MACROS_VERSION(1.10) + [m4_fatal([must install xorg-macros 1.12 or later before running autoconf/autogen])]) +XORG_MACROS_VERSION(1.12) XORG_DEFAULT_OPTIONS XORG_ENABLE_SPECS -XORG_WITH_XMLTO(0.0.20) +XORG_WITH_XMLTO(0.0.22) XORG_WITH_FOP -XORG_CHECK_SGML_DOCTOOLS(1.5) +XORG_WITH_XSLTPROC +XORG_CHECK_SGML_DOCTOOLS(1.8) AC_OUTPUT([Makefile specs/Makefile diff --git a/docbook.am b/docbook.am new file mode 100644 index 0000000..bba4d54 --- /dev/null +++ b/docbook.am @@ -0,0 +1,105 @@ +# +# Generate output formats for a single DocBook/XML with/without chapters +# +# Variables set by the calling Makefile: +# shelfdir: the location where the docs/specs are installed. Typically $(docdir) +# docbook: the main DocBook/XML file, no chapters, appendix or image files +# chapters: all files pulled in by an XInclude statement and images. +# + +# +# This makefile is intended for Users Documentation and Functional Specifications. +# Do not use for Developer Documentation which is not installed and does not require olink. +# Refer to http://www.x.org/releases/X11R7.6/doc/xorg-docs/ReleaseNotes.html#id2584393 +# for an explanation on documents classification. +# + +# DocBook/XML generated output formats to be installed +shelf_DATA = + +# DocBook/XML file with chapters, appendix and images it includes +dist_shelf_DATA = $(docbook) $(chapters) + +if HAVE_XMLTO +if HAVE_STYLESHEETS + +XMLTO_SEARCHPATH_FLAGS = \ + --searchpath "$(XORG_SGML_PATH)/X11" \ + --searchpath "$(abs_top_builddir)" +XMLTO_HTML_OLINK_FLAGS = \ + --stringparam target.database.document=$(XORG_SGML_PATH)/X11/dbs/masterdb.html.xml \ + --stringparam current.docid="$(<:.xml=)" +XMLTO_HTML_STYLESHEET_FLAGS = -x $(STYLESHEET_SRCDIR)/xorg-xhtml.xsl +XMLTO_HTML_FLAGS = \ + $(XMLTO_SEARCHPATH_FLAGS) \ + $(XMLTO_HTML_STYLESHEET_FLAGS) \ + $(XMLTO_HTML_OLINK_FLAGS) + +shelf_DATA += $(docbook:.xml=.html) +%.html: %.xml $(chapters) + $(AM_V_GEN)$(XMLTO) $(XMLTO_HTML_FLAGS) xhtml-nochunks $< + +if HAVE_XMLTO_TEXT + +shelf_DATA += $(docbook:.xml=.txt) +%.txt: %.xml $(chapters) + $(AM_V_GEN)$(XMLTO) $(XMLTO_HTML_FLAGS) txt $< +endif HAVE_XMLTO_TEXT + +if HAVE_FOP +XMLTO_FO_IMAGEPATH_FLAGS = --stringparam img.src.path=$(abs_builddir)/ +XMLTO_PDF_OLINK_FLAGS = \ + --stringparam target.database.document=$(XORG_SGML_PATH)/X11/dbs/masterdb.pdf.xml \ + --stringparam current.docid="$(<:.xml=)" +XMLTO_FO_STYLESHEET_FLAGS = -x $(STYLESHEET_SRCDIR)/xorg-fo.xsl + +XMLTO_FO_FLAGS = \ + $(XMLTO_SEARCHPATH_FLAGS) \ + $(XMLTO_FO_STYLESHEET_FLAGS) \ + $(XMLTO_FO_IMAGEPATH_FLAGS) \ + $(XMLTO_PDF_OLINK_FLAGS) + +shelf_DATA += $(docbook:.xml=.pdf) +%.pdf: %.xml $(chapters) + $(AM_V_GEN)$(XMLTO) $(XMLTO_FO_FLAGS) --with-fop pdf $< + +shelf_DATA += $(docbook:.xml=.ps) +%.ps: %.xml $(chapters) + $(AM_V_GEN)$(XMLTO) $(XMLTO_FO_FLAGS) --with-fop ps $< +endif HAVE_FOP + +# Generate documents cross-reference target databases +if HAVE_XSLTPROC + +XSLT_SEARCHPATH_FLAGS = \ + --path "$(XORG_SGML_PATH)/X11" \ + --path "$(abs_top_builddir)" +XSLT_OLINK_FLAGS = \ + --stringparam targets.filename "$@" \ + --stringparam collect.xref.targets "only" \ + --stringparam olink.base.uri "$(@:.db=)" + +XSLT_HTML_FLAGS = \ + $(XSLT_SEARCHPATH_FLAGS) \ + $(XSLT_OLINK_FLAGS) \ + --nonet --xinclude \ + $(STYLESHEET_SRCDIR)/xorg-xhtml.xsl +XSLT_PDF_FLAGS = \ + $(XSLT_SEARCHPATH_FLAGS) \ + $(XSLT_OLINK_FLAGS) \ + --nonet --xinclude \ + $(STYLESHEET_SRCDIR)/xorg-fo.xsl + +shelf_DATA += $(docbook:.xml=.html.db) +%.html.db: %.xml $(chapters) + $(AM_V_GEN)$(XSLTPROC) $(XSLT_HTML_FLAGS) $< + +shelf_DATA += $(docbook:.xml=.pdf.db) +%.pdf.db: %.xml $(chapters) + $(AM_V_GEN)$(XSLTPROC) $(XSLT_PDF_FLAGS) $< + +endif HAVE_XSLTPROC +endif HAVE_STYLESHEETS +endif HAVE_XMLTO + +CLEANFILES = $(shelf_DATA) diff --git a/packaging/xorg-x11-proto-scrnsaver.spec b/packaging/xorg-x11-proto-scrnsaver.spec new file mode 100644 index 0000000..ca42bf8 --- /dev/null +++ b/packaging/xorg-x11-proto-scrnsaver.spec @@ -0,0 +1,45 @@ +Name: xorg-x11-proto-scrnsaver +Summary: X.Org X11 Protocol scrnsaverproto +Version: 1.2.2 +Release: 1 +Group: Development/System +License: MIT +URL: http://www.x.org +Source0: %{name}-%{version}.tar.gz +Provides: scrnsaverproto + +BuildRequires: pkgconfig +BuildRequires: pkgconfig(xorg-macros) + +# some file to be intalled can be ignored when rpm generates packages +%define _unpackaged_files_terminate_build 0 + +%description +Description: %{summary} + +%prep +%setup -q + +%build + +./autogen.sh +%reconfigure --disable-static \ + --libdir=%{_datadir} \ + --without-xmlto + +# Call make instruction with smp support +make %{?jobs:-j%jobs} + +%install +rm -rf %{buildroot} +%make_install + +%remove_docs + +%clean +rm -rf %{buildroot} + +%files +%defattr(-,root,root,-) +%{_includedir}/X11/extensions/*.h +%{_datadir}/pkgconfig/*.pc \ No newline at end of file diff --git a/packaging/xorg-x11-proto-scrnsaverproto.spec b/packaging/xorg-x11-proto-scrnsaverproto.spec deleted file mode 100644 index 101b494..0000000 --- a/packaging/xorg-x11-proto-scrnsaverproto.spec +++ /dev/null @@ -1,50 +0,0 @@ - -Name: xorg-x11-proto-scrnsaverproto -Summary: X.Org X11 Protocol scrnsaverproto -Version: 1.2.1 -Release: 1 -Group: Development/System -License: MIT -URL: http://www.x.org -Source0: http://xorg.freedesktop.org/releases/individual/proto/scrnsaverproto-%{version}.tar.gz -Provides: scrnsaverproto -BuildRequires: pkgconfig(xorg-macros) - - -%description -Description: %{summary} - - - -%prep -%setup -q -n scrnsaverproto-%{version} - -%build - -%reconfigure --disable-static \ - --libdir=%{_datadir} - -# Call make instruction with smp support -make %{?jobs:-j%jobs} - -%install -rm -rf %{buildroot} -%make_install - - -%clean -rm -rf %{buildroot} - - - - - - -%files -%defattr(-,root,root,-) -%{_datadir}/pkgconfig/scrnsaverproto.pc -%{_docdir}/scrnsaverproto/saver.xml -%{_includedir}/X11/extensions/saver.h -%{_includedir}/X11/extensions/saverproto.h - - diff --git a/specs/Makefile.am b/specs/Makefile.am old mode 100755 new mode 100644 index a312ac9..f93e295 --- a/specs/Makefile.am +++ b/specs/Makefile.am @@ -1,64 +1,13 @@ -# -# Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved. -# -# Permission is hereby granted, free of charge, to any person obtaining a -# copy of this software and associated documentation files (the "Software"), -# to deal in the Software without restriction, including without limitation -# the rights to use, copy, modify, merge, publish, distribute, sublicense, -# and/or sell copies of the Software, and to permit persons to whom the -# Software is furnished to do so, subject to the following conditions: -# -# The above copyright notice and this permission notice (including the next -# paragraph) shall be included in all copies or substantial portions of the -# Software. -# -# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL -# THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING -# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER -# DEALINGS IN THE SOFTWARE. -# if ENABLE_SPECS -doc_sources = saver.xml -dist_doc_DATA = $(doc_sources) -if HAVE_XMLTO -doc_DATA = $(doc_sources:.xml=.html) +# Main DocBook/XML files (DOCTYPE book) +docbook = saver.xml -if HAVE_FOP -doc_DATA += $(doc_sources:.xml=.ps) $(doc_sources:.xml=.pdf) -endif +# The location where the DocBook/XML files and their generated formats are installed +shelfdir = $(docdir) -if HAVE_XMLTO_TEXT -doc_DATA += $(doc_sources:.xml=.txt) -endif +# Generate DocBook/XML output formats with or without stylesheets +include $(top_srcdir)/docbook.am -if HAVE_STYLESHEETS -XMLTO_FLAGS = -m $(XSL_STYLESHEET) - -doc_DATA += xorg.css -xorg.css: $(STYLESHEET_SRCDIR)/xorg.css - $(AM_V_GEN)cp -pf $(STYLESHEET_SRCDIR)/xorg.css $@ -endif - -CLEANFILES = $(doc_DATA) - -SUFFIXES = .xml .ps .pdf .txt .html - -.xml.txt: - $(AM_V_GEN)$(XMLTO) $(XMLTO_FLAGS) txt $< - -.xml.html: - $(AM_V_GEN)$(XMLTO) $(XMLTO_FLAGS) xhtml-nochunks $< - -.xml.pdf: - $(AM_V_GEN)$(XMLTO) $(XMLTO_FLAGS) --with-fop pdf $< - -.xml.ps: - $(AM_V_GEN)$(XMLTO) $(XMLTO_FLAGS) --with-fop ps $< - -endif HAVE_XMLTO endif ENABLE_SPECS diff --git a/specs/saver.xml b/specs/saver.xml old mode 100755 new mode 100644 index 93b5229..2374218 --- a/specs/saver.xml +++ b/specs/saver.xml @@ -1,29 +1,35 @@ <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" - "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"> + "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" +[ +<!ENTITY % defs SYSTEM "defs.ent"> %defs; +]> <book id="saver"> <bookinfo> <title>X11 Screen Saver Extension MIT X Consortium Proposed Standard + X Version 11, Release &fullrelvers; Version 1.0 - + JimFulton Network Computing Devices, Inc - - + + KeithPackard X Consortium, Laboratory for Computer Science, Massachusetts Institute of Technology - + - 1992Massachusetts Institute of Technology and Network Computing Devices, Inc + 1992 + Massachusetts Institute of Technology + Network Computing Devices, Inc + - X Version 11, Release 5 @@ -39,9 +45,7 @@ implied warranty. - -TITLE - + Introduction The X Window System provides support for changing the image on a display screen @@ -61,9 +65,9 @@ particular, such users often wish to be able to display corporate logos, instructions on how to reactivate the screen, and automatic screen-locking utilities. This extension provides a means for writing such clients. - + - + Assumptions This extension exports the notion of a special screen saver window that is @@ -73,9 +77,9 @@ the window manager. Furthermore, the X identifier for the window is never returned by QueryTree requests on the root window, so it is typically not visible to other clients. - + - + Overview The core @@ -106,9 +110,9 @@ id for the screen saver window and setting the attributes (e.g. size, location, visual, colormap) to be used when the window is mapped. These requirements form the basis of this extension. - + - + Issues This extension raises several interesting issues. First is the question of @@ -130,33 +134,34 @@ it is not mapped so that it need not be avoided during event delivery. Thus, screen saver clients may find that the requests that reference the screen saver window may fail when the window is not displayed. - + - + Protocol The Screen Saver extension is as follows: - + Types In adition to the comon types described in the core protocol, the following type is used in the request and event definitions in subsequent sections. - - - - + + + + + - + Name Value - + SCREENSAVEREVENT ScreenSaverNotify, ScreenSaverCycle @@ -164,16 +169,16 @@ type is used in the request and event definitions in subsequent sections. - + - + Errors The Screen Saver extension adds no errors beyond the core protocol. - + - + Requests The Screen Saver extension adds the following requests: @@ -232,11 +237,12 @@ active and how the til-or-since value should be i - - - + + + + - + Off The screen is not currently being saved; @@ -245,7 +251,7 @@ specifies the number of milliseconds until the screen saver is expected to activate. - + On The screen is currently being saved; @@ -253,7 +259,7 @@ The screen is currently being saved; the number of milliseconds since the screen saver activated. - + Disabled The screen saver is currently disabled; @@ -270,21 +276,22 @@ used or would have been were the screen being saved: - - - + + + + - + Blanked The video signal to the display monitor was disabled. - + Internal A server-dependent, built-in screen saver image was displayed; either no client had set the screen saver window attributes or a different client had the server grabbed when the screen saver activated. - + External The screen saver window was mapped with attributes set by a client using the ScreenSaverSetAttributes request. @@ -328,18 +335,19 @@ Otherwise, any combination of the following bits may be set: - - - + + + + - + ScreenSaverNotify If this bit is set, ScreenSaverNotify events are generated whenever the screen saver is activated or deactivated. - + ScreenSaverCycle If this bit is set, ScreenSaverNotify events are generated whenever @@ -464,9 +472,9 @@ deactivation. This request is ignored if the client has not previously set the screen saver window attributes. - + - + Events The Screen Saver extension adds one event: @@ -500,25 +508,26 @@ The state field specifies the cause of the event: - - - + + + + - + Off The screen saver deactivated; this event is sent if the client has set the ScreenSaverNotify bit in its event mask. - + On The screen saver activated. This event is sent if the client has set the ScreenSaverNotify bit in its event mask. - + Cycle The cycle interval passed and the client is expected to change the image on @@ -550,10 +559,10 @@ when the screen saver was activated, as described in The time field indicates the server time when the event was generated. - + - + Encoding Please refer to the X11 Protocol Encoding document as this document uses @@ -563,16 +572,16 @@ conventions established there. The name of this extension is "SCREEN-SAVER". - + Common Types SETofSCREENSAVEREVENT #x00000001 ScreenSaverNotifyMask #x00000002 ScreenSaverCycleMask - + - + Requests ScreenSaverQueryVersion @@ -649,9 +658,9 @@ SETofSCREENSAVEREVENT 2 3 request length 4 DRAWABLE drawable associated with screen - + - + Events @@ -672,10 +681,10 @@ SETofSCREENSAVEREVENT 1 BOOL forced 14 unused - + - + Inter-Client Communications Conventions Screen saver clients should create at least one resource value whose @@ -691,9 +700,9 @@ resource and should be one of the following: FONT, or COLORMAP. - + - + C language binding @@ -707,7 +716,7 @@ The include file for this extension is - + Bool XScreenSaverQueryExtension Display *display @@ -730,7 +739,7 @@ no additional errors are defined by this extension, the results of error_base are not defined. - + Status XScreenSaverQueryVersion Display *display @@ -755,14 +764,14 @@ set and 0 is returned. This routine allocates and returns an XScreenSaverInfo structure -for use in calls to XScreenSaverQueryInfo. +for use in calls to . All fields in the structure are initialized to zero. If insufficient memory is available, NULL is returned. The results of this routine can be released -using XFree. +using XFree. - + Status XScreenSaverQueryInfo Display *display @@ -797,7 +806,7 @@ description of the fields. If the extension is not supported, is returned. - + void XScreenSaverSelectInput Display *display @@ -834,7 +843,7 @@ See the definition of the of the allowed event masks. - + void XScreenSaverSetAttributes Display *dpy @@ -860,7 +869,7 @@ of the ScreenSaverSetAttributes request for a description of each of the arguments. - + void XScreenSaverUnsetAttributes Display *display @@ -874,7 +883,7 @@ extension, this routine instructs the server to discard any previous screen saver window attributes set by this client. - + Status XScreenSaverRegister Display *display @@ -893,7 +902,7 @@ is encountered and the property is not changed, otherwise it returns non-zero. - + Status XScreenSaverUnregister Display *display @@ -908,7 +917,7 @@ It returns zero if an error is encountered and the property is changed, otherwise it returns non-zero. - + Status XScreenSaverGetRegistered Display *display @@ -930,6 +939,5 @@ is encountered or if the property does not exist or is not of the correct format; otherwise it returns non-zero. - -- 2.7.4