UNKNOWN
Project description
Introduction
============
``mr.developer`` is a ``zc.buildout`` extension which makes it easier to work with
buildouts containing lots of packages of which you only want to develop some.
The basic idea for this comes from Wichert Akkerman's ``plonenext`` effort.
Usage
-----
You add ``mr.developer`` to the ``extensions`` option of your ``[buildout]``
section. Then you can add the following options to your ``[buildout]``
section:
``sources-dir``
This specifies where your development packages should be placed. Defaults
to ``src``.
``sources-svn``
This specifies a section which lists the subversion repository URLs of
your packages.
``sources-git``
This specifies a section which lists the git repository URLs of your
packages.
``auto-checkout``
This specifies the names of packages which should be checked out during
buildout, packages already checked out are skipped.
The following is an example of how your ``buildout.cfg`` may look like::
[buildout]
...
extensions = mr.developer
sources-svn = sources-svn
sources-git = sources-git
auto-checkout = my.package
[sources-svn]
my.package = http://example.com/svn/my.package/trunk
[sources-git]
some.other.package = git://example.com/git/some.other.package.git
When you run buildout, you will get a script at ``bin/checkout`` in your
buildout directory. With that script you can checkout the source from the
specified repository, without the need to know where the repository is
located.
Now if you run buildout again, the package is automatically marked as an
develop egg and, if it's listed in the section specified by the ``versions``
option in the ``[buildout]`` section, the version will be set to an empty
string, so the develop egg will actually be used.
Help text of checkout script
----------------------------
.. include:: docs/CHECKOUT.txt
Changelog
=========
0.6 - 2009-03-24
----------------
* Added custom logging formatter for nicer output in the checkout script.
[fschulze]
* Removed the '-e' option, regular expression matching is the default now.
[fschulze]
* Made it possible to specify more than one regular expression without the
need to use a pipe symbol and quotes.
[fschulze]
* Added help text for the checkout script to pypi page.
[fschulze]
* Add a warning to rerun buildout after checkout.
[fschulze]
0.5 - 2009-03-23
----------------
* Make sure that the updated versions are actually used.
[fschulze]
0.4 - 2009-03-22
----------------
* Fixed logging, which fixes the info message output.
[fschulze]
* Skip checkout of existing packages.
[fschulze]
0.3 - 2009-03-22
----------------
* Fixed source distribution by adding a MANIFEST.in.
[fschulze]
* Added -e and -l options to checkout script.
[fschulze]
0.2 - 2009-03-22
----------------
* Added ``auto-checkout`` option (only works with subversion at the moment).
[fschulze]
* Added support for git.
[fschulze]
* Throw error when trying to checkout unknown package.
[fschulze]
* Fixed target directory for checkouts.
[fschulze]
0.1 - 2009-03-19
----------------
* Initial release
============
``mr.developer`` is a ``zc.buildout`` extension which makes it easier to work with
buildouts containing lots of packages of which you only want to develop some.
The basic idea for this comes from Wichert Akkerman's ``plonenext`` effort.
Usage
-----
You add ``mr.developer`` to the ``extensions`` option of your ``[buildout]``
section. Then you can add the following options to your ``[buildout]``
section:
``sources-dir``
This specifies where your development packages should be placed. Defaults
to ``src``.
``sources-svn``
This specifies a section which lists the subversion repository URLs of
your packages.
``sources-git``
This specifies a section which lists the git repository URLs of your
packages.
``auto-checkout``
This specifies the names of packages which should be checked out during
buildout, packages already checked out are skipped.
The following is an example of how your ``buildout.cfg`` may look like::
[buildout]
...
extensions = mr.developer
sources-svn = sources-svn
sources-git = sources-git
auto-checkout = my.package
[sources-svn]
my.package = http://example.com/svn/my.package/trunk
[sources-git]
some.other.package = git://example.com/git/some.other.package.git
When you run buildout, you will get a script at ``bin/checkout`` in your
buildout directory. With that script you can checkout the source from the
specified repository, without the need to know where the repository is
located.
Now if you run buildout again, the package is automatically marked as an
develop egg and, if it's listed in the section specified by the ``versions``
option in the ``[buildout]`` section, the version will be set to an empty
string, so the develop egg will actually be used.
Help text of checkout script
----------------------------
.. include:: docs/CHECKOUT.txt
Changelog
=========
0.6 - 2009-03-24
----------------
* Added custom logging formatter for nicer output in the checkout script.
[fschulze]
* Removed the '-e' option, regular expression matching is the default now.
[fschulze]
* Made it possible to specify more than one regular expression without the
need to use a pipe symbol and quotes.
[fschulze]
* Added help text for the checkout script to pypi page.
[fschulze]
* Add a warning to rerun buildout after checkout.
[fschulze]
0.5 - 2009-03-23
----------------
* Make sure that the updated versions are actually used.
[fschulze]
0.4 - 2009-03-22
----------------
* Fixed logging, which fixes the info message output.
[fschulze]
* Skip checkout of existing packages.
[fschulze]
0.3 - 2009-03-22
----------------
* Fixed source distribution by adding a MANIFEST.in.
[fschulze]
* Added -e and -l options to checkout script.
[fschulze]
0.2 - 2009-03-22
----------------
* Added ``auto-checkout`` option (only works with subversion at the moment).
[fschulze]
* Added support for git.
[fschulze]
* Throw error when trying to checkout unknown package.
[fschulze]
* Fixed target directory for checkouts.
[fschulze]
0.1 - 2009-03-19
----------------
* Initial release
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
mr.developer-0.6.zip
(10.2 kB
view hashes)