[Checkins] SVN: Sandbox/mlundwall/introspector.zope2/trunk/ Initial
import.
Martin Lundwall
martin at webworks.se
Thu Jun 26 05:35:16 EDT 2008
Log message for revision 87794:
Initial import.
Changed:
A Sandbox/mlundwall/introspector.zope2/trunk/INSTALL.txt
A Sandbox/mlundwall/introspector.zope2/trunk/README.txt
A Sandbox/mlundwall/introspector.zope2/trunk/bootstrap.py
A Sandbox/mlundwall/introspector.zope2/trunk/buildout.cfg
A Sandbox/mlundwall/introspector.zope2/trunk/configs/
A Sandbox/mlundwall/introspector.zope2/trunk/configs/base.cfg
A Sandbox/mlundwall/introspector.zope2/trunk/configs/development.cfg
A Sandbox/mlundwall/introspector.zope2/trunk/configs/production.cfg
A Sandbox/mlundwall/introspector.zope2/trunk/newlinesfix.sh
A Sandbox/mlundwall/introspector.zope2/trunk/remove-svndirs.sh
A Sandbox/mlundwall/introspector.zope2/trunk/src/
A Sandbox/mlundwall/introspector.zope2/trunk/src/EXTERNALS.txt
A Sandbox/mlundwall/introspector.zope2/trunk/src/README.txt
A Sandbox/mlundwall/introspector.zope2/trunk/svnconfig-for-plone.txt
A Sandbox/mlundwall/introspector.zope2/trunk/versions-to-pin.sh
-=-
Added: Sandbox/mlundwall/introspector.zope2/trunk/INSTALL.txt
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/INSTALL.txt (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/INSTALL.txt 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,15 @@
+Buildout needs Python 2.4.4 and Zope needs a C-compiler
+
+On Debian/Ubuntu, install: python2.4 python2.4-dev build-essential
+
+Locate the system python and run "easy_install virtualenv"
+
+Run "virtualenv python" in your buildout directory. You can change the name python to anything suitable. This will create a python executable + all libs.
+
+Run bootstrap and buildout with the new python:
+./python/bin/python2.4 bootstrap.py (Python might be called something else)
+./bin/buildout (Fetches all the packages)
+./bin/instance fg (Starts the server in debug-mode/foreground)
+
+Play ball!
+/Robin
Added: Sandbox/mlundwall/introspector.zope2/trunk/README.txt
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/README.txt (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/README.txt 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,327 @@
+=======================
+Using a custom buildout
+=======================
+
+Note: If you are using Windows, if you do not have PIL installed, or you are
+not using Python 2.4 as your main system Python, please see the relevant
+sections below.
+
+You probably got here by running something like:
+
+ $ paster create -t plone3_buildout
+
+Now, you need to run:
+
+ $ python bootstrap.py
+
+This will install zc.buildout for you.
+
+To create an instance immediately, run:
+
+ $ bin/buildout
+
+This will download Plone's eggs and products for you, as well as other
+dependencies, create a new Zope 2 installation (unless you specified
+an existing one when you ran "paster create"), and create a new Zope instance
+configured with these products.
+
+You can start your Zope instance by running:
+
+ $ bin/instance start
+
+or, to run in foreground mode:
+
+ $ bin/instance fg
+
+To run unit tests, you can use:
+
+ $ bin/instance test -s my.package
+
+Installing PIL
+--------------
+
+To use Plone, you need PIL, the Python Imaging Library. If you don't already
+have this, download and install it from http://www.pythonware.com/products/pil.
+
+Using a different Python installation
+--------------------------------------
+
+Buildout will use your system Python installation by default. However, Zope
+2.10 (and by extension, Plone) will only work with Python 2.4. You can verify
+which version of Python you have, by running:
+
+ $ python -V
+
+If that is not a 2.4 version, you need to install Python 2.4 from
+http://python.org. If you wish to keep another version as your main system
+Python, edit buildout.cfg and add an 'executable' option to the "[buildout]"
+section, pointing to a python interpreter binary:
+
+ [buildout]
+ ...
+ executable = /path/to/python
+
+Working with buildout.cfg
+-------------------------
+
+You can change any option in buildout.cfg and re-run bin/buildout to reflect
+the changes. This may delete things inside the 'parts' directory, but should
+keep your Data.fs and source files intact.
+
+To save time, you can run buildout in "offline" (-o) and non-updating (-N)
+mode, which will prevent it from downloading things and checking for new
+versions online:
+
+ $ bin/buildout -Nov
+
+Creating new eggs
+-----------------
+
+New packages you are working on (but which are not yet released as eggs and
+uploaded to the Python Package Index, aka PYPI) should be placed in src. You can do:
+
+ $ cd src/
+ $ paster create -t plone my.package
+
+Use "paster create --list-templates" to see all available templates. Answer
+the questions and you will get a new egg. Then tell buildout about your egg
+by editing buildout.cfg and adding your source directory to 'develop':
+
+ [buildout]
+ ...
+ develop =
+ src/my.package
+
+You can list multiple packages here, separated by whitespace or indented
+newlines.
+
+You probably also want the Zope instance to know about the package. Add its
+package name to the list of eggs in the "[instance]" section, or under the
+main "[buildout]" section:
+
+ [instance]
+ ...
+ eggs =
+ ${buildout:eggs}
+ ${plone:eggs}
+ my.package
+
+Leave the ${buildout:eggs} part in place - it tells the instance to use the
+eggs that buildout will have downloaded from the Python Package Index
+previously.
+
+If you also require a ZCML slug for your package, buildout can create one
+automatically. Just add the package to the 'zcml' option:
+
+ [instance]
+ ...
+ zcml =
+ my.package
+
+When you are finished, re-run buildout. Offline, non-updating mode should
+suffice:
+
+ $ bin/buildout -Nov
+
+Developing old-style products
+-----------------------------
+
+If you are developing old-style Zope 2 products (not eggs) then you can do so
+by placing the product code in the top-level 'products' directory. This is
+analogous to the 'Products/' directory inside a normal Zope 2 instance and is
+scanned on start-up for new products.
+
+Depending on a new egg
+----------------------
+
+If you want to use a new egg that is in the Python Package Index, all you need
+to do is to add it to the "eggs" option under the main "[buildout]" section:
+
+ [buildout]
+ ...
+ eggs =
+ my.package
+
+If it's listed somewhere else than the Python Package Index, you can add a link
+telling buildout where to find it in the 'find-links' option:
+
+ [buildout]
+ ...
+ find-links =
+ http://dist.plone.org
+ http://download.zope.org/distribution/
+ http://effbot.org/downloads
+ http://some.host.com/packages
+
+Using existing old-style products
+---------------------------------
+
+If you are using an old-style (non-egg) product, you can either add it as an
+automatically downloaded archive or put it in the top-level "products" folder.
+The former is probably better, because it means you can redistribute your
+buildout.cfg more easily:
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+ http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+
+If someproduct-1.3.tar.gz extracts into several products inside a top-level
+directory, e.g. SomeProduct-1.3/PartOne and SomeProduct-1.3/PartTwo, then
+add it as a "nested package":
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+ http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+ nested-packages =
+ someproduct-1.3.tar.gz
+
+Alternatively, if it extracts to a directory which contains the version
+number, add it as a "version suffix package":
+
+ [productdistros]
+ recipe = plone.recipe.distros
+ urls =
+ http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz
+ version-suffix-packages =
+ someproduct-1.3.tar.gz
+
+You can also track products by adding a new bundle checkout part. It
+doesn't strictly have to be an svn bundle at all, any svn location will do,
+and cvs is also supported:
+
+ [buildout]
+ ...
+ parts =
+ plone
+ zope2
+ productdistros
+ myproduct
+ instance
+ zopepy
+
+Note that "myproduct" comes before the "instance" part. You then
+need to add a new section to buildout.cfg:
+
+ [myproduct]
+ recipe = plone.recipe.bundlecheckout
+ url = http://svn.plone.org/svn/collective/myproduct/trunk
+
+Finally, you need to tell Zope to find this new checkout and add it to its
+list of directories that are scanned for products:
+
+ [instance]
+ ...
+ products =
+ ${buildout:directory}/products
+ ${productdistros:location}
+ ${plonebundle:location}
+ ${myproduct:location}
+
+Without this last step, the "myproduct" part is simply managing an svn
+checkout and could potentially be used for something else instead.
+
+=============
+Using Windows
+=============
+
+To use buildout on Windows, you will need to install a few dependencies which
+other platforms manage on their own.
+
+Here are the steps you need to follow (thanks to Hanno Schlichting for these):
+
+Python (http://python.org)
+--------------------------
+
+ - Download and install Python 2.4.4 using the Windows installer from
+ http://www.python.org/ftp/python/2.4.4/python-2.4.4.msi
+ Select 'Install for all users' and it will put Python into the
+ "C:\Python24" folder by default.
+
+ - You also want the pywin32 extensions available from
+ http://downloads.sourceforge.net/pywin32/pywin32-210.win32-py2.4.exe?modtime=1159009237&big_mirror=0
+
+ - And as a last step you want to download the Python imaging library available
+ from http://effbot.org/downloads/PIL-1.1.6.win32-py2.4.exe
+
+ - If you develop Zope based applications you will usually only need Python 2.4
+ at the moment, so it's easiest to put the Python binary on the systems PATH,
+ so you don't need to specify its location manually each time you call it.
+
+ Thus, put "C:\Python24" and "C:\Python24\Scripts" onto the PATH. You can
+ find the PATH definition in the control panel under system preferences on
+ the advanced tab at the bottom. The button is called environment variables.
+ You want to add it at the end of the already existing PATH in the system
+ section. Paths are separated by a semicolons.
+
+ - You can test if this was successful by opening a new shell (cmd) and type
+ in 'python -V'. It should report version 2.4.4 (or whichever version you
+ installed).
+
+ Opening a new shell can be done quickly by using the key combination
+ 'Windows-r' or if you are using Parallels on a Mac 'Apple-r'. Type in 'cmd'
+ into the popup box that opens up and hit enter.
+
+
+Subversion (http://subversion.tigris.org)
+-----------------------------------------
+
+ - Download the nice installer from
+ http://subversion.tigris.org/files/documents/15/35379/svn-1.4.2-setup.exe
+
+ - Run the installer. It defaults to installing into
+ "C:\Program Files\Subversion".
+
+ - Now put the install locations bin subfolder (for example
+ "C:\Program Files\Subversion\bin") on your system PATH in the same way you
+ put Python on it.
+
+ - Open a new shell again and type in: 'svn --version' it should report
+ version 1.4.2 or newer.
+
+
+MinGW (http://www.mingw.org/)
+-----------------------------
+
+ This is a native port of the gcc compiler and its dependencies for Windows.
+ There are other approaches enabling you to compile Python C extensions on
+ Windows including Cygwin and using the official Microsoft C compiler, but this
+ is a lightweight approach that uses only freely available tools. As
+ it's used by a lot of people chances are high it will work for you and there's
+ plenty of documentation out there to help you in troubleshooting problems.
+
+ - Download the MinGW installer from
+ http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe?modtime=1168794334&big_mirror=1
+
+ - The installer will ask you which options you would like to install. Choose
+ base and make here. It will install into "C:\MinGW" by default. The install
+ might take some time as it's getting files from sourceforge.net and you
+ might need to hit 'retry' a couple of times.
+
+ - Now put the install location's bin subfolder (for example "C:\MinGW\bin") on
+ your system PATH in the same way you put Python on it.
+
+ - Test this again by typing in: 'gcc --version' on a newly opened shell and
+ it should report version 3.4.2 or newer.
+
+
+Configure Distutils to use MinGW
+--------------------------------
+
+ Some general information are available from
+ http://www.mingw.org/MinGWiki/index.php/Python%20extensions for example but
+ you don't need to read them all.
+
+ - Create a file called 'distutils.cfg' in "C:\Python24\Lib\distutils". Open it
+ with a text editor ('notepad distutils.cfg') and fill in the following lines:
+
+ [build]
+ compiler=mingw32
+
+ This will tell distutils to use MinGW as the default compiler, so you don't
+ need to specify it manually using "--compiler=mingw32" while calling a
+ package's setup.py with a command that involves building C extensions. This
+ is extremely useful if the build command is written down in a buildout
+ recipe where you cannot change the options without hacking the recipe
+ itself. The z2c.recipe.zope2install used in ploneout is one such example.
Added: Sandbox/mlundwall/introspector.zope2/trunk/bootstrap.py
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/bootstrap.py (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/bootstrap.py 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,55 @@
+##############################################################################
+#
+# Copyright (c) 2006 Zope Corporation and Contributors.
+# All Rights Reserved.
+#
+# This software is subject to the provisions of the Zope Public License,
+# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution.
+# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
+# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
+# FOR A PARTICULAR PURPOSE.
+#
+##############################################################################
+"""Bootstrap a buildout-based project
+
+Simply run this script in a directory containing a buildout.cfg.
+The script accepts buildout command-line options, so you can
+use the -c option to specify an alternate configuration file.
+
+$Id: bootstrap.py 2 2008-01-22 10:58:59Z lregebro $
+"""
+
+import os, shutil, sys, tempfile, urllib2
+
+tmpeggs = tempfile.mkdtemp()
+
+try:
+ import pkg_resources
+except ImportError:
+ ez = {}
+ exec urllib2.urlopen('http://peak.telecommunity.com/dist/ez_setup.py'
+ ).read() in ez
+ ez['use_setuptools'](to_dir=tmpeggs, download_delay=0)
+
+ import pkg_resources
+
+cmd = 'from setuptools.command.easy_install import main; main()'
+if sys.platform == 'win32':
+ cmd = '"%s"' % cmd # work around spawn lamosity on windows
+
+ws = pkg_resources.working_set
+assert os.spawnle(
+ os.P_WAIT, sys.executable, sys.executable,
+ '-c', cmd, '-mqNxd', tmpeggs, 'zc.buildout',
+ dict(os.environ,
+ PYTHONPATH=
+ ws.find(pkg_resources.Requirement.parse('setuptools')).location
+ ),
+ ) == 0
+
+ws.add_entry(tmpeggs)
+ws.require('zc.buildout')
+import zc.buildout.buildout
+zc.buildout.buildout.main(sys.argv[1:] + ['bootstrap'])
+shutil.rmtree(tmpeggs)
Added: Sandbox/mlundwall/introspector.zope2/trunk/buildout.cfg
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/buildout.cfg (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/buildout.cfg 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,2 @@
+[buildout]
+extends = configs/development.cfg
Added: Sandbox/mlundwall/introspector.zope2/trunk/configs/base.cfg
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/configs/base.cfg (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/configs/base.cfg 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,168 @@
+[buildout]
+parts =
+ plone
+ zope2
+ productdistros
+ instance
+ zopepy
+
+# Add additional egg download sources here. dist.plone.org contains archives
+# of Plone packages.
+find-links =
+ http://dist.plone.org
+ http://download.zope.org/ppix/
+ http://download.zope.org/distribution/
+ http://effbot.org/downloads
+
+# Add additional eggs here
+# elementtree is required by Plone
+eggs =
+ elementtree
+ PILwoTk
+# Products.LinguaPlone
+# BeautifulSoup
+ zope.introspector
+
+# Reference any eggs you are developing here, one per line
+# e.g.: develop = src/my.package
+develop =
+ src/zope.introspector
+
+newest = false
+versions = versions
+
+[versions]
+
+
+[plone]
+recipe = plone.recipe.plone >=3.0,<3.1dev
+#recipe = plone.recipe.plone == 3.1.1
+#recipe = plone.recipe.plone25install
+url =
+# http://plone.googlecode.com/files/Plone-2.5.4-final.tar.gz
+eggs =
+
+[zope2]
+recipe = plone.recipe.zope2install
+url = ${plone:zope2-url}
+
+# Use this section to download additional old-style products.
+# List any number of URLs for product tarballs under URLs (separate
+# with whitespace, or break over several lines, with subsequent lines
+# indented). If any archives contain several products inside a top-level
+# directory, list the archive file name (i.e. the last part of the URL,
+# normally with a .tar.gz suffix or similar) under 'nested-packages'.
+# If any archives extract to a product directory with a version suffix, list
+# the archive name under 'version-suffix-packages'.
+[productdistros]
+recipe = plone.recipe.distros
+urls =
+nested-packages =
+version-suffix-packages =
+
+[instance]
+recipe = plone.recipe.zope2instance
+zope2-location = ${zope2:location}
+http-address = 8080
+debug-mode = off
+verbose-security = off
+user = admin:admin
+
+
+# If you want Zope to know about any additional eggs, list them here.
+# This should include any development eggs you listed in develop-eggs above,
+# e.g. eggs = ${buildout:eggs} ${plone:eggs} my.package
+eggs =
+ ${buildout:eggs}
+ ${plone:eggs}
+
+# If you want to register ZCML slugs for any packages, list them here.
+# e.g. zcml = my.package my.other.package
+zcml =
+ zope.introspector
+
+products =
+ ${buildout:directory}/products
+ ${productdistros:location}
+ ${plone:products}
+
+[zopepy]
+recipe = zc.recipe.egg
+eggs =
+ ${buildout:eggs}
+ ${plone:eggs}
+interpreter = zopepy
+extra-paths = ${zope2:location}/lib/python
+scripts = zopepy
+
+#[zeoserver]
+#recipe = plone.recipe.zope2zeoserver
+#zope2-location = ${zope2:location}
+#zeo-address = 8100
+
+#[private-client]
+#recipe = plone.recipe.zope2instance
+#zope2-location = ${zope2:location}
+#zeo-client = true
+#zeo-address = 8100
+#zodb-cache-size = 5000
+#zeo-client-cache-size = 300MB
+#user = admin:admin
+#http-address = 8080
+#debug-mode = off
+#verbose-security = off
+#eggs =
+# ${plone:eggs}
+# ${buildout:eggs}
+#zcml =
+#
+#products =
+# ${buildout:directory}/products
+# ${productdistros:location}
+# ${plone:products}
+
+#[public-client-1]
+#recipe = plone.recipe.zope2instance
+#zope2-location = ${zope2:location}
+#zeo-client = true
+#zeo-address = 8100
+#zodb-cache-size = 5000
+#zeo-client-cache-size = 300MB
+#user = ${private-client:user}
+#http-address = 8081
+#debug-mode = off
+#verbose-security = off
+#eggs = ${private-client:eggs}
+#zcml = ${private-client:zcml}
+#products = ${private-client:products}
+#zope-conf-additional =
+# zserver-threads 1
+
+#[varnish-build]
+#recipe = plone.recipe.varnish:build
+#url = http://downloads.sourceforge.net/varnish/varnish-1.1.2.tar.gz
+
+#[varnish-instance]
+#recipe = plone.recipe.varnish:instance
+#bind = 127.0.0.1:8280
+#backends =
+# 127.0.0.1:8180
+#cache-size = 1G
+
+#[pound]
+#recipe = iw.recipe.pound
+#owner = jorgen
+#group = jorgen
+#url = http://www.apsis.ch/pound/Pound-2.3.2.tgz
+#balancers =
+# main 8180 127.0.0.1:8080 127.0.0.1:8081
+
+#[apache-build]
+#recipe = tl.buildout_apache:httpd
+#url = http://netmirror.org/mirror/apache.org/httpd/httpd-2.2.8.tar.gz
+#md5sum = 39a755eb0f584c279336387b321e3dfc
+
+#[apache-instance]
+#recipe = tl.buildout_apache:root
+#httpd = apache-build
+
Added: Sandbox/mlundwall/introspector.zope2/trunk/configs/development.cfg
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/configs/development.cfg (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/configs/development.cfg 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,10 @@
+[buildout]
+extends = base.cfg
+
+[instance]
+http-address = 8080
+debug-mode = on
+verbose-security = on
+user = admin:admin
+
+#Should perhaps have introspection and docfinder tab?
\ No newline at end of file
Added: Sandbox/mlundwall/introspector.zope2/trunk/configs/production.cfg
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/configs/production.cfg (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/configs/production.cfg 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,15 @@
+[buildout]
+extends = base.cfg
+#parts =
+# plone
+# zope2
+# productdistros
+# zopepy
+# zeoserver
+# private-client
+# public-client-1
+# varnish-build
+# varnish-instance
+# pound
+# apache-build
+# apache-instance
\ No newline at end of file
Added: Sandbox/mlundwall/introspector.zope2/trunk/newlinesfix.sh
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/newlinesfix.sh (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/newlinesfix.sh 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,21 @@
+#The script previously known as Jorgen the cleaner. Fixes inconsistent newlines before checkin.
+
+if [ ! -e $1 ]; then
+ if [ "$1"=="" ]; then
+ echo "Usage: newlinesfix.sh <filename>"
+ echo "The old file will be saved as <filename>.old"
+ exit 1
+ fi
+fi
+
+
+cp $1 $1".old"
+if [ ! -e $1".old" ] ; then
+ echo "Failed to make backup copy of old file. Exiting..."
+ exit 1
+fi
+
+
+cat $1".old" | perl -n -e "s/\r/\n/g;print" > $1
+
+echo "All done. Happyness and all that."
\ No newline at end of file
Property changes on: Sandbox/mlundwall/introspector.zope2/trunk/newlinesfix.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: Sandbox/mlundwall/introspector.zope2/trunk/remove-svndirs.sh
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/remove-svndirs.sh (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/remove-svndirs.sh 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,12 @@
+#!/bin/bash
+#This is just a script to remove the .svn directories.
+
+if [ ! -e ./remove-svndirs.sh ] ; then
+ echo "This script must be run from the same directory as it exists in."
+ exit 1
+ fi
+
+find . -name ".svn" -type d -exec echo "removing:" {} \; -exec rm -rf {} \;
+
+echo "All done. It's a good idea to remove this script now."
+exit 0
\ No newline at end of file
Property changes on: Sandbox/mlundwall/introspector.zope2/trunk/remove-svndirs.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: Sandbox/mlundwall/introspector.zope2/trunk/src/EXTERNALS.txt
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/src/EXTERNALS.txt (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/src/EXTERNALS.txt 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1 @@
+zope.introspector svn+ssh://mlundwall@svn.zope.org/repos/main/zope.introspector/trunk
\ No newline at end of file
Added: Sandbox/mlundwall/introspector.zope2/trunk/src/README.txt
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/src/README.txt (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/src/README.txt 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1 @@
+Packages in eggs that you develop should go in this directory
Added: Sandbox/mlundwall/introspector.zope2/trunk/svnconfig-for-plone.txt
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/svnconfig-for-plone.txt (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/svnconfig-for-plone.txt 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,116 @@
+### This file configures various client-side behaviors.
+###
+### The commented-out examples below are intended to demonstrate
+### how to use this file.
+
+### Section for authentication and authorization customizations.
+[auth]
+### Set store-passwords to 'no' to avoid storing passwords in the
+### auth/ area of your config directory. It defaults to 'yes'.
+### Note that this option only prevents saving of *new* passwords;
+### it doesn't invalidate existing passwords. (To do that, remove
+### the cache files by hand as described in the Subversion book.)
+# store-passwords = no
+### Set store-auth-creds to 'no' to avoid storing any subversion
+### credentials in the auth/ area of your config directory.
+### It defaults to 'yes'. Note that this option only prevents
+### saving of *new* credentials; it doesn't invalidate existing
+### caches. (To do that, remove the cache files by hand.)
+# store-auth-creds = no
+
+### Section for configuring external helper applications.
+[helpers]
+### Set editor to the command used to invoke your text editor.
+### This will override the environment variables that Subversion
+### examines by default to find this information ($EDITOR,
+### et al).
+# editor-cmd = editor (vi, emacs, notepad, etc.)
+### Set diff-cmd to the absolute path of your 'diff' program.
+### This will override the compile-time default, which is to use
+### Subversion's internal diff implementation.
+# diff-cmd = diff_program (diff, gdiff, etc.)
+### Set diff3-cmd to the absolute path of your 'diff3' program.
+### This will override the compile-time default, which is to use
+### Subversion's internal diff3 implementation.
+# diff3-cmd = diff3_program (diff3, gdiff3, etc.)
+### Set diff3-has-program-arg to 'true' or 'yes' if your 'diff3'
+### program accepts the '--diff-program' option.
+# diff3-has-program-arg = [true | false]
+
+### Section for configuring tunnel agents.
+[tunnels]
+### Configure svn protocol tunnel schemes here. By default, only
+### the 'ssh' scheme is defined. You can define other schemes to
+### be used with 'svn+scheme://hostname/path' URLs. A scheme
+### definition is simply a command, optionally prefixed by an
+### environment variable name which can override the command if it
+### is defined. The command (or environment variable) may contain
+### arguments, using standard shell quoting for arguments with
+### spaces. The command will be invoked as:
+### <command> <hostname> svnserve -t
+### (If the URL includes a username, then the hostname will be
+### passed to the tunnel agent as <user>@<hostname>.) If the
+### built-in ssh scheme were not predefined, it could be defined
+### as:
+# ssh = $SVN_SSH ssh
+### If you wanted to define a new 'rsh' scheme, to be used with
+### 'svn+rsh:' URLs, you could do so as follows:
+# rsh = rsh
+### Or, if you wanted to specify a full path and arguments:
+# rsh = /path/to/rsh -l myusername
+### On Windows, if you are specifying a full path to a command,
+### use a forward slash (/) or a paired backslash (\\) as the
+### path separator. A single backslash will be treated as an
+### escape for the following character.
+
+# For protocol svn+examplessh:// instead of standard
+# examplessh = /usr/bin/ssh -p 10022
+
+### Section for configuring miscelleneous Subversion options.
+[miscellany]
+### Set global-ignores to a set of whitespace-delimited globs
+### which Subversion will ignore in its 'status' output, and
+### while importing or adding files and directories.
+global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store *.pyc *.tmp *.pyo
+
+### Set log-encoding to the default encoding for log messages
+# log-encoding = latin1
+### Set use-commit-times to make checkout/update/switch/revert
+### put last-committed timestamps on every file touched.
+# use-commit-times = yes
+### Set no-unlock to prevent 'svn commit' from automatically
+### releasing locks on files.
+# no-unlock = yes
+### Set enable-auto-props to 'yes' to enable automatic properties
+### for 'svn add' and 'svn import', it defaults to 'no'.
+### Automatic properties are defined in the section 'auto-props'.
+enable-auto-props = yes
+
+### Section for configuring automatic properties.
+[auto-props]
+### The format of the entries is:
+### file-name-pattern = propname[=value][;propname[=value]...]
+### The file-name-pattern can contain wildcards (such as '*' and
+### '?'). All entries which match will be applied to the file.
+### Note that auto-props functionality must be enabled, which
+### is typically done by setting the 'enable-auto-props' option.
+# *.c = svn:eol-style=native
+# *.cpp = svn:eol-style=native
+# *.h = svn:eol-style=native
+# *.dsp = svn:eol-style=CRLF
+# *.dsw = svn:eol-style=CRLF
+# Makefile = svn:eol-style=native
+*.sh = svn:eol-style=native;svn:executable
+*.gif = svn:mime-type=image/gif
+*.png = svn:mime-type=image/png
+*.jpg = svn:mime-type=image/jpeg
+*.txt = svn:eol-style=native
+*.py = svn:eol-style=native
+*.cpy = svn:eol-style=native
+*.vpy = svn:eol-style=native
+*.pt = svn:eol-style=native
+*.cpt = svn:eol-style=native
+*.dtml = svn:eol-style=native
+*.zcml = svn:eol-style=native
+*.js = svn:eol-style=native
+*.metadata = svn:eol-style=native
\ No newline at end of file
Added: Sandbox/mlundwall/introspector.zope2/trunk/versions-to-pin.sh
===================================================================
--- Sandbox/mlundwall/introspector.zope2/trunk/versions-to-pin.sh (rev 0)
+++ Sandbox/mlundwall/introspector.zope2/trunk/versions-to-pin.sh 2008-06-26 09:34:47 UTC (rev 87794)
@@ -0,0 +1,12 @@
+#!/bin/bash
+#This is just a script to show what versions that need to be pinned in buildout.
+
+if [ ! -e ./bin/buildout ] ; then
+ echo "This script needs buildout to be in bin/buildout."
+ exit 1
+ fi
+
+./bin/buildout -Novvvvv |sed -ne 's/^Picked: //p' | sort | uniq
+
+#echo "All done. It's a good idea to remove this script now."
+exit 0
\ No newline at end of file
Property changes on: Sandbox/mlundwall/introspector.zope2/trunk/versions-to-pin.sh
___________________________________________________________________
Name: svn:executable
+ *
More information about the Checkins
mailing list