Re: [Repoze-dev] bfg vs buildout
Am Wed, 24 Jun 2009 10:54:33 +0100 schrieb Chris Withers:
Hey All,
Just been reading http://docs.repoze.org/bfg/narr/install.html and I
notice a conspicuous absence of zc.buildout...
Do you guys recommend not using buildout? If not, are there docs
anywhere for using BFG in a buildout context?
I do use zc.buildout. Here an minimal example:
-
[buildout]
extensions = buildout.dumppickedversions
parts = instance
eggs-directory = ${buildout:directory}/eggs
find-links =
http://dist.repoze.org/bfg/1.0/
[instance]
recipe = repoze.recipe.egg:scripts
eggs =
repoze.bfg
Missing is a version fixation like done in ZTK, Grok, Plone, ...
I'd really like to see such a version.cfg for each repoze release.
Creation could be automated.
hth greetz
--
Jens W. Klein - Klein Partner KEG - BlueDynamics Alliance
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] understanding setup of repoze.what
I have some problems with the setup of repoze.what in the docs [1] theres a 'quickstart' mentioned. Also theres written: Warning Do not try to configure repoze.who directly – if you want authorization to work, you have to configure it through repoze.what. [1] http://what.repoze.org/docs/1.x/Manual/GettingStarted.html Fine so far. Before looking at repoze.what at all i made repoze.who work. Its pretty simple (just a basic auth, but enough for my scenario). I have an ini-file which configures it all. Now if it comes to repoze.what it seems theres no ini-file-configuration possible. Except maybe with 'quickstart', but 'quickstart' isnt documented at all (at least its not linked at [1] and I do not find any documentation nor hwo to get it into repoze.what). Also at [2], the place where I'd expect more details on quickstart, theres only unsufficiant information available. [2] http://what.repoze.org/docs/1.x/Manual/Plugins/ Can someone enlighten me how to use it in the proposed paster build environment? thanks in advance and best regards -- Jens W. Klein - Klein Partner KEG - BlueDynamics Alliance ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] understanding setup of repoze.what
Am Fri, 05 Jun 2009 13:34:16 +0200 schrieb Gustavo Narea: [...] The ability to configure repoze.what from a .ini file will be built-in as of repoze.what-1.1.0, which I hope to release this month, possibly forked from and backwards-compatible with the plugin above. is there already any code i can checkout, use and test already in your VCS? HTH, Yes, a lot! Thanks! Jens -- Jens W. Klein - Klein Partner KEG - BlueDynamics Alliance ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] make repoze dists more buildout friendly
Hi, I'am using buildout and repoze.bfg. It worked fine until i came to the point where i tried to integrate repoze.what. repoze.what is on pypi, repoze.who is on an own index server. Now i came up with a solution (please please document this somewhere), here the minimal buildout: --snip- [buildout] parts = instance find-links = http://dist.repoze.org/bfg/1.0/ [instance] recipe = repoze.recipe.egg:scripts eggs = repoze.what repoze.bfg --/snip- The major disadvantage over using the index= approach is: Version pinning is needed to be done manually (the extension buildout.dumppickedversions helps a lot here). Why not put a version.cfg file at http://dist.repoze.org/bfg/1.0/ version.cfg for all files in there? It should be easy to auto-create such from the files in the directory. This would make repoze.bfg distributions more buildout-friendly and also documents explizit the dependend versions used in the specific bundle. Additional i learned today the major difference between find-links and index in buildout (at the end in setuptools), as wiggy said: find-links= expects a directory with files in it, index= expects a directory with a subdirectory for every package Odd enough, but its setuptools. regards -- Jens W. Klein - Klein Partner KEG - BlueDynamics Alliance ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
