Permalink
Browse files

refactored cumulus to use autconf for installation. should make creation

of RPMs and DEBs much easier.
  • Loading branch information...
BuzzTroll
BuzzTroll committed Jun 8, 2010
1 parent 50be5b1 commit 8f50fa15c175f048fb2c0c31d5aac01deb8a892e
Showing with 3,236 additions and 443 deletions.
  1. +1 −0 cumulus/AUTHORS
  2. +674 −0 cumulus/COPYING
  3. 0 cumulus/ChangeLog
  4. +302 −0 cumulus/INSTALL
  5. +7 −0 cumulus/MANIFEST.in
  6. +59 −0 cumulus/Makefile.am
  7. 0 cumulus/NEWS
  8. 0 cumulus/{docs/README.txt → README}
  9. +951 −0 cumulus/aclocal.m4
  10. +27 −0 cumulus/configure.ac
  11. +30 −0 cumulus/cumulus-install.sh
  12. +0 −26 cumulus/etc/cumulus.ini.in
  13. +0 −26 cumulus/etc/cumulus_test.ini.in
  14. +0 −9 cumulus/etc/env.2.in
  15. +0 −19 cumulus/etc/env.sh.in
  16. +0 −284 cumulus/ez_setup.py
  17. +520 −0 cumulus/install-sh
  18. +0 −78 cumulus/install.sh
  19. +376 −0 cumulus/missing
  20. 0 cumulus/{ → src}/bin/base-repo.py
  21. 0 cumulus/{ → src}/bin/cloudfs-adduser.sh
  22. 0 cumulus/{ → src}/bin/cloudfs-chmod.sh
  23. 0 cumulus/{ → src}/bin/cloudfs-list-user.sh
  24. 0 cumulus/{ → src}/bin/cloudfs-ls.sh
  25. 0 cumulus/{ → src}/bin/cloudfs-quota.sh
  26. 0 cumulus/{ → src}/bin/cloudfs-stat.sh
  27. 0 cumulus/{ → src}/bin/cloudfs-touch.sh
  28. 0 cumulus/{ → src}/bin/cumulus-add-user.sh
  29. 0 cumulus/{ → src}/bin/cumulus-list-users.sh
  30. 0 cumulus/{ → src}/bin/cumulus-quota.sh
  31. 0 cumulus/{ → src}/bin/cumulus-remove-user.sh
  32. 0 cumulus/{ → src}/bin/cumulus.sh
  33. 0 cumulus/{ → src}/bin/new-user.sh
  34. +1 −1 cumulus/{ → src}/docs/QUICKSTART.txt
  35. 0 cumulus/{ → src}/docs/README.authz.txt
  36. +193 −0 cumulus/src/docs/README.txt
  37. 0 cumulus/{ → src}/etc/acl.sql
  38. +26 −0 cumulus/src/etc/cumulus.ini.in
  39. +24 −0 cumulus/src/etc/cumulus_tests.ini.in
  40. +26 −0 cumulus/src/etc/cumulus_tests_https.ini.in
  41. 0 cumulus/{ → src}/etc/dot_s3cfg.in
  42. +19 −0 cumulus/src/etc/env.sh.in
  43. 0 cumulus/{ → src}/etc/testcert.pem
  44. 0 cumulus/{ → src}/etc/testkey.pem
  45. 0 cumulus/{ → src}/pycb/__init__.py
  46. 0 cumulus/{ → src}/pycb/cbAuthzSecurity.py
  47. 0 cumulus/{ → src}/pycb/cbBackendInterface.py
  48. 0 cumulus/{ → src}/pycb/cbException.py
  49. 0 cumulus/{ → src}/pycb/cbMakeErrorDict.py
  50. 0 cumulus/{ → src}/pycb/cbObject.py
  51. 0 cumulus/{ → src}/pycb/cbPosixBackend.py
  52. 0 cumulus/{ → src}/pycb/cbPosixSecurity.py
  53. 0 cumulus/{ → src}/pycb/cbRequest.py
  54. 0 cumulus/{ → src}/pycb/cumulus.py
  55. 0 cumulus/{ → src}/pycb/test_common.py
  56. 0 cumulus/{ → src}/pycb/tools/__init__.py
  57. 0 cumulus/{ → src}/pycb/tools/add_user.py
  58. 0 cumulus/{ → src}/pycb/tools/cbToolsException.py
  59. 0 cumulus/{ → src}/pycb/tools/list_users.py
  60. 0 cumulus/{ → src}/pycb/tools/remove_user.py
  61. 0 cumulus/{ → src}/pycb/tools/set_quota.py
  62. 0 cumulus/{ → src}/pynimbusauthz/__init__.py
  63. 0 cumulus/{ → src}/pynimbusauthz/add_user.py
  64. 0 cumulus/{ → src}/pynimbusauthz/authz_exception.py
  65. 0 cumulus/{ → src}/pynimbusauthz/chmod.py
  66. 0 cumulus/{ → src}/pynimbusauthz/cmd_opts.py
  67. 0 cumulus/{ → src}/pynimbusauthz/db.py
  68. 0 cumulus/{ → src}/pynimbusauthz/list_user.py
  69. 0 cumulus/{ → src}/pynimbusauthz/ls.py
  70. 0 cumulus/{ → src}/pynimbusauthz/objects.py
  71. 0 cumulus/{ → src}/pynimbusauthz/quota.py
  72. 0 cumulus/{ → src}/pynimbusauthz/stat.py
  73. 0 cumulus/{ → src}/pynimbusauthz/touch.py
  74. 0 cumulus/{ → src}/pynimbusauthz/user.py
  75. 0 cumulus/{ → src}/setup.py
  76. 0 cumulus/{ → src}/tests/authz/file_test.py
  77. 0 cumulus/{ → src}/tests/authz/qutoa_test.py
  78. 0 cumulus/{ → src}/tests/authz/test_add_user.py
  79. 0 cumulus/{ → src}/tests/authz/test_chmod.py
  80. 0 cumulus/{ → src}/tests/authz/test_list_user.py
  81. 0 cumulus/{ → src}/tests/authz/test_ls.py
  82. 0 cumulus/{ → src}/tests/authz/test_opts.py
  83. 0 cumulus/{ → src}/tests/authz/test_stat.py
  84. 0 cumulus/{ → src}/tests/authz/test_touch.py
  85. 0 cumulus/{ → src}/tests/authz/user_tests.py
  86. 0 cumulus/{ → src}/tests/authz/userfile_test.py
  87. 0 cumulus/{ → src}/tests/client/auth_tests.py
  88. 0 cumulus/{ → src}/tests/client/buckets_test.py
  89. 0 cumulus/{ → src}/tests/client/pub_auth_tests.py
  90. 0 cumulus/{ → src}/tests/client/quota_test.py
  91. 0 cumulus/{ → src}/tests/client/simple_auth.py
  92. 0 cumulus/{ → src}/tests/client/simple_test.py
  93. 0 cumulus/{ → src}/tests/client/user_tests.py
  94. 0 cumulus/{ → src}/tests/run-all.sh
  95. 0 cumulus/{ → src}/tests/run-pass.sh
  96. 0 cumulus/{ → src}/tests/s3cmd/run-em.sh
  97. 0 cumulus/{ → src}/tests/s3cmd/test_basic_bucket.sh
  98. 0 cumulus/{ → src}/tests/s3cmd/test_basic_transfer.sh
  99. 0 cumulus/{ → src}/tests/s3cmd/test_connection_drop.sh
  100. 0 cumulus/{ → src}/tests/s3cmd/test_drop_gets.sh
  101. 0 cumulus/{ → src}/tests/s3cmd/test_info.sh
  102. 0 cumulus/{ → src}/tests/s3cmd/test_la.sh
  103. 0 cumulus/{ → src}/tests/s3cmd/test_list_root.sh
  104. 0 cumulus/{ → src}/tests/s3cmd/test_put_same_time.sh
  105. 0 cumulus/{ → src}/tests/s3cmd/test_recursive_delete.sh
  106. 0 cumulus/{ → src}/tests/s3cmd/test_recursive_xfer.sh
  107. 0 cumulus/{ → src}/virtualenv.py
View
@@ -0,0 +1 @@
+The Nimbus Team
View

Large diffs are not rendered by default.

Oops, something went wrong.
View
No changes.
View
@@ -0,0 +1,302 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008, 2009 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 -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.
+
View
@@ -0,0 +1,7 @@
+include install.sh
+include docs/QUICKSTART.txt
+include docs/README.authz.txt
+include docs/README.txt
+include virtualenv.py
+recursive-include tests *
+recursive-include etc *
View
@@ -0,0 +1,59 @@
+
+MAINTAINERCLEANFILES = \
+ $(srcdir)/INSTALL \
+ $(srcdir)/aclocal.m4 \
+ $(srcdir)/autoscan.log \
+ $(srcdir)/compile \
+ $(srcdir)/config.guess \
+ $(srcdir)/config.h.in \
+ $(srcdir)/config.sub \
+ $(srcdir)/configure \
+ $(srcdir)/configure.scan \
+ $(srcdir)/depcomp \
+ $(srcdir)/install-sh \
+ $(srcdir)/ltmain.sh \
+ $(srcdir)/missing \
+ $(srcdir)/mkinstalldirs
+
+version=0.1
+cumulus_src_dir=$(srcdir)/src
+cumulus_pydist_dir=$(cumulus_src_dir)/dist/cumulus-$(version)
+cumulus_dst_dir=$(prefix)
+authz_bk_up=$(cumulus_dst_dir)/etc/authz.db.bak
+
+clean:
+ rm -rf $(srcdir)/dist
+ rm -rf $(srcdir)/cumulus.egg-info
+ rm -rf $(srcdir)/cumulus-$(version)
+ rm -rf $(cumulus_pydist_dir)
+
+installclean:
+ rm -rf $(cumulus_dst_dir)
+
+predest:
+ mkdir -p $(cumulus_dst_dir)
+ mkdir -p $(cumulus_dst_dir)/log
+
+virtenv:
+ $(PYTHON) $(cumulus_src_dir)/virtualenv.py -p $(PYTHON) --no-site-packages $(cumulus_dst_dir)
+
+pydist: virtenv
+ (cd $(cumulus_src_dir) && $(cumulus_dst_dir)/bin/python ./setup.py sdist)
+ (cd $(cumulus_src_dir)/dist && tar -zxvf cumulus-$(version).tar.gz)
+
+tests:
+ (cd $(cumulus_dst_dir)/tests && ./run-all.sh)
+
+all: clean predest virtenv pydist
+ echo "done"
+
+install: all
+ cp $(cumulus_src_dir)/etc/cumulus.ini ~/.nimbus
+ cp -r $(cumulus_src_dir)/tests $(cumulus_dst_dir)
+ cp -r $(cumulus_src_dir)/docs $(cumulus_dst_dir)
+ cp -r $(cumulus_src_dir)/etc $(cumulus_dst_dir)
+ cp -r $(cumulus_src_dir)/etc/env.sh $(cumulus_dst_dir)
+ (cd $(cumulus_pydist_dir) && $(cumulus_dst_dir)/bin/python ./setup.py install)
+ $(SQLITE) -batch $(cumulus_dst_dir)/etc/authz.db < $(cumulus_src_dir)/etc/acl.sql
+ echo "done"
+
View
No changes.
File renamed without changes.
Oops, something went wrong.

0 comments on commit 8f50fa1

Please sign in to comment.