mlhim-owners team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 68
committer: Timothy W. Cook <timothywayne.cook@xxxxxxxxx>
branch nick: hkcr
timestamp: Sat 2011-05-28 17:42:58 -0500
message:
  Corrected teh HKCR buildout configuration so that it doesn't mess with installed system settings.  Renamed it to hkcr.develop.cfg.  Updated install FAQ.
removed:
  hkcr.buildout.cfg
added:
  hkcr.develop.cfg


--
lp:hkcr
https://code.launchpad.net/~hkcr-dev/hkcr/hkcr

Your team Multi-level Healthcare Information Modelling Owners is subscribed to branch lp:hkcr.
To unsubscribe from this branch go to https://code.launchpad.net/~hkcr-dev/hkcr/hkcr/+edit-subscription

=== removed file 'hkcr.buildout.cfg'
--- hkcr.buildout.cfg	2011-05-28 22:02:38 +0000
+++ hkcr.buildout.cfg	1970-01-01 00:00:00 +0000
@@ -1,200 +0,0 @@
-############################################
-#
-# Buildout Configuration File for Standalone Plone
-# ------------------------------------------------
-# $LastChangedDate: 2011-04-10 09:34:13 -0700 (Sun, 10 Apr 2011) $ $LastChangedRevision: 47921M $
-#
-# After making changes in this configuration file,
-# you should run bin/buildout to update the components.
-# 
-# ALWAYS back up all Plone/Zope data and components
-# before changing configuration.
-# 
-# Running "bin/buildout" will update your installation,
-# installing missing components as necessary.
-# 
-# Use "bin/buildout -n" to update many components here to the newest
-# available releases.
-# This will update the add-on products you've added in the eggs= lines.
-# This will not, however, upgrade Plone itself (or anything else you've
-# pinned with a version specification). To upgrade Plone itself, see the
-# comments in "Plone Component Versions".
-#
-# Tutorial instructions for using zc.buildout for
-# configuration management are available at:
-# http://plone.org/documentation/tutorial/buildout
-# Full details at http://pypi.python.org/pypi/zc.buildout
-#
-############################################
-
-
-[buildout]
-
-############################################
-# Plone Component Versions
-# ------------------------
-# This version of the Unified Installer has the components of Plone 4 
-# preloaded so that it can install without an Internet connection.
-# If you want to update, uncomment the "http://..."; line below,
-# edit it to point to the current version URL, comment out the 
-# "versions.cfg" line and run "bin/buildout" while attached to the 
-# Internet. Generally, you only want to do that as part of a planned migration.
-# Note that if you are updating components, you should also check the versions
-# section at the end of this file, since recipes or components other than
-# those of Zope and Plone may need updating at the same time.
-#
-extends = 
-    base.cfg
-    versions.cfg
-#    http://dist.plone.org/release/4.0-latest/versions.cfg
-
-
-############################################
-# Ports
-# -----
-# Specify the port on which your Zope installation
-# will listen:
-http-address = 8080
-
-
-# If you try to start Zope as root, it will change user id to run as
-# the effective user specified here. This user id must own the var directory
-# of your buildout.
-effective-user = tim
-
-
-############################################
-# Eggs
-# ----
-# Add an indented line to the eggs section for any Python
-# eggs or packages you wish to include.
-#
-eggs =
-    Plone
-    PIL==1.1.6
-    hkcr.theme
-    hkcr.cddfile
-    collective.zipfiletransport
-    
-# Optional Functionality
-# ----------------------
-# Uncomment the indented lines to include these add-on products.
-# Documentation on all of them, along with many more products,
-# is available at
-# http://plone.org/products/
-#
-# Example products:
-# * LinguaPlone provides tools for building multi-lingual sites
-# * PloneFormGen provides through-the-web form building
-#
-#    Products.LinguaPlone==4.0.1
-#    Products.PloneFormGen==1.6.0
-#
-# Note that versions may be specified here or in the [versions]
-# section below. You should always specify versions that you know
-# are compatible with the Plone release and at an acceptable
-# development level.
-#
-# Commonly used development tools:
-# Several excellent development tools are included in the develop.cfg
-# buildout extension. Read it to learn how to activate these tools.
-
-    
-############################################
-# ZCML Slugs
-# ----------
-# Some eggs need ZCML slugs to tell Zope to
-# use them. This is increasingly rare.
-zcml =
-#    plone.reload
-     
-############################################
-# Development Eggs
-# ----------------
-# You can use paster to create "development eggs" to
-# develop new products/themes. Put these in the src/
-# directory.
-# You will also need to add the egg names in the
-# eggs section above, and may also need to add them
-# to the zcml section.
-#
-# Provide the *paths* to the eggs you are developing here:
-develop =
-#    src/my.package
-     src/hkcr/hkcr.theme
-     src/hkcr/hkcr.cddfile
-     
-############################################
-# Debug Mode
-# ----------
-# Change debug-mode to "on" to run in development mode.
-# This will dramatically slow Plone.
-# 
-debug-mode = off
-# Add-on developers should turn deprecation warnings on
-deprecation-warnings = off
-# change verbose-security to "on" for useful security errors while developing
-verbose-security = off
-
-
-############################################
-# Backup Directory
-# ----------------
-# Sets the target directory for the bin/backup and bin/snapshotbackup
-# commands. Default is inside this project's var directory, but ideally
-# this should be on a separate volume or backup server.
-# 
-backups-dir=${buildout:directory}/var
-
-
-############################################
-# Initial User
-# ------------
-# This is the user id and password that will be used to create the initial 
-# user id that will allow you to log in and create a Plone site. This only
-# sets the initial password; it will not allow you to change an already 
-# existing password. If you change the admin password via the web interface,
-# the one below will no longer be valid.
-# If you find yourself locked out of your Zope/Python installation, you may
-# add an emergency user via "bin/plonectl adduser".
-user=admin:aoJUwB3C
-
-
-############################################
-# Parts Specification
-#--------------------
-# Specifies the components that should be included in the buildout.
-# All the basics are in the base.cfg extension; you may add your
-# own if you need them at the end of this file.
-parts =
-    instance
-    zopepy
-    zopeskel
-    unifiedinstaller
-    chown
-
-
-############################################
-# Versions Specification
-# ----------------------
-# Version information supplied here will "pin" Python packages to a particular
-# version number, even when you use the "newest" flag running buildout.
-# Specifying versions for all packages is a good idea and can prevent
-# accidental changes when you add new packages to your buildout.
-# Note that versions specified here will override those specified earlier
-# in the configuration, including those from the Plone and Zope version
-# config files.
-#
-[versions] 
-Cheetah = 2.2.1
-Paste = 1.7.5.1
-PasteScript = 1.7.3
-ZopeSkel = 2.19
-collective.recipe.backup = 1.7
-plone.recipe.command = 1.1
-plone.recipe.osxcontroller = 0.4
-plone.recipe.unifiedinstaller = 4.0rc1
-
-#Required by:
-#PasteScript 1.7.3
-PasteDeploy = 1.3.4

=== added file 'hkcr.develop.cfg'
--- hkcr.develop.cfg	1970-01-01 00:00:00 +0000
+++ hkcr.develop.cfg	2011-05-28 22:42:58 +0000
@@ -0,0 +1,149 @@
+#################################################################
+#
+#    Development Configuration
+#    =========================
+#    
+#    This is a buildout configuration that sets up a development
+#    environment for Plone. It extends buildout.cfg.
+#    
+#    To use this configuration, run buildout via:
+#    
+#    bin/buildout -c develop.cfg
+#    
+#    This specifies develop.cfg as buildout's configuration file. This configuration
+#    file extends buildout.cfg, so that all the options from that file are 
+#    automatically included.
+#    
+#    Included in the development configuration
+#    
+#    Common development tools:
+#    
+#     * paster and Zopeskel, an add-on skeleton construction kit.
+#     
+#     * mr.developer, a tool that automatically checks out source for
+#       add ons from a versioning system, then adds them to your
+#       development package list.
+#       
+#     * testrunner, which provides a command-line option to run
+#       test suites.
+#     
+#     * omelette, which automatically musters python package sources
+#       into parts/omelette for easy find / grep access.
+#     
+#     * DocFinderTab, which adds a "doc" tab to the ZMI to explore documentation
+#       for the current Zope object.
+#
+#     * plone.reload, which allows you to use a URL like http://localhost:8080/@@reload
+#       to reload Python and ZCML code without restarting Zope.
+# 
+#     Common Customizations
+#     =====================
+#     
+#     Add packages to the sources managed by mr.developer by adding them to the
+#     [sources] section below.
+#     
+#     Add packages to the test suite by adding them to the "test-packages" option
+#     in the [buildout] section below.
+
+
+############################################
+# Sources
+# -------
+# Specify packages under development here.
+#
+# See http://pypi.python.org/pypi/mr.developer for mr.developer source specifications.
+# <name> = <kind> [key=value] <url> [path] [key=value]
+# kind = The kind of repository. Currently supported are one of svn (>= 1.5), hg, git, cvs or fs.
+#
+[sources]
+# Examples: to check out plonetheme.sunburst from Plone's svn, use:
+# plonetheme.sunburst = svn https://svn.plone.org/svn/plone/plonetheme.sunburst/trunk
+#
+# To use a python package that is being developed in your src subdirectory, use:
+# myproduct.betterplone = fs myproduct.betterplone
+
+
+
+[buildout]
+
+############################################
+# Test Packages
+# ----------
+# Specify a list of packages that you wish to include in your test suite.
+# These packages will have their included tests run when you invoke
+# bin/test
+#
+test-packages =
+#    plonetheme.sunburst
+
+
+############################################
+# Debug Mode
+# ----------
+# Most development work is done with Zope/Plone started
+# in foreground mode (bin/plonectl fg), which automatically
+# turns on debug mode and causes Zope/Plone to stop on
+# package loading errors.
+#
+# Note that debug mode makes Plone run *very* slowly due to
+# extra filesystem checks and granular transmission of browser resources.
+#
+# If you have a need to run in debug mode outside foreground
+# operation, turn on debug mode below.
+debug-mode = off
+#
+# If you're developing Plone add-ons, you should want to see
+# deprecation warnings that let you know if you're using outmoded
+# methods or modules.
+deprecation-warnings = on
+#
+# Turning on verbose security may help diagnose security bugs.
+# You'll also need to disable the intercepting of "unauthorized"
+# errors in the error_log via the ZMI.
+verbose-security = off
+
+
+############################################
+# Less Commonly Changed Options
+# -----------------------------
+# The remainder of the buildout mainly sets up the development
+# environment based on the settings above.
+
+# we're extending buildout.cfg
+extends =
+    buildout.cfg
+
+extensions +=
+    mr.developer
+
+eggs +=
+    Products.DocFinderTab
+    plone.reload
+    hkcr.theme
+    hkcr.cddfile
+    collective.zipfiletransport
+
+parts +=
+    test
+    zopeskel
+    omelette
+
+# mr.developer settings:
+always-checkout = force
+sources = sources
+auto-checkout = *
+
+
+[omelette]
+recipe = collective.recipe.omelette
+eggs = ${buildout:eggs}
+
+
+[test]
+recipe = zc.recipe.testrunner
+defaults = ['--auto-color', '--auto-progress']
+
+eggs =
+    ${buildout:test-packages}
+
+