[Product-Developers] Re: archgenxml 2.4.1 doesn't generate setup.py
Mirto Silvio Busico
mirtosilvio.busico at fastwebnet.it
Wed Jun 3 07:42:57 UTC 2009
Mybe I'm very dumb, but:
I create the skeleton egg with paster and I don't have any src directory.
The command I used in the products directory is:
sudo ../bin/paster create -t archetype products.msbgas3
But I obtain this tree (without any src directory):
mirto at msb02:/usr/local/Plone/zeocluster/products$ tree .
.
|-- README.txt
`-- products.msbgas3
|-- CHANGES.txt
|-- CONTRIBUTORS.txt
|-- MANIFEST.in
|-- README.txt
|-- docs
| |-- HISTORY.txt
| |-- INSTALL.txt
| |-- LICENSE.GPL
| `-- LICENSE.txt
|-- msbgas3
| |-- __init__.py
| `-- msbgas3
| |-- README.txt
| |-- __init__.py
| |-- browser
| | |-- __init__.py
| | |-- __init__.pyo
| | `-- configure.zcml
| |-- config.py
| |-- configure.zcml
| |-- content
| | |-- __init__.py
| | |-- __init__.pyo
| | `-- configure.zcml
| |-- interfaces
| | |-- __init__.py
| | `-- __init__.pyo
| |-- portlets
| | |-- __init__.py
| | |-- __init__.pyo
| | `-- configure.zcml
| |-- profiles
| | `-- default
| | |-- factorytool.xml
| | |-- metadata.xml
| | |-- portlets.xml
| | `-- types.xml
| `-- tests
| |-- __init__.py
| |-- __init__.pyo
| |-- base.py
| `-- test_doctest.py
|-- products.msbgas3.egg-info
| |-- PKG-INFO
| |-- SOURCES.txt
| |-- dependency_links.txt
| |-- entry_points.txt
| |-- namespace_packages.txt
| |-- not-zip-safe
| |-- requires.txt
| `-- top_level.txt
|-- setup.cfg
`-- setup.py
I'm using the wrong template?
Thanks
Mirto
Jens W. Klein ha scritto:
> Am Tue, 02 Jun 2009 21:07:09 +0200 schrieb Mirto Silvio Busico:
>
>
>> Hi all,
>>
>> I'm trying to start to (re)develop plone products. My experience was
>> with the 2.5 way.
>>
>> First I installed le latest plone with unified installer (with zeo
>> parameter).
>>
>> Now I'm trying to create a new product with archgenxml 2.4.1 (from
>> pypi). I create the helloworld product and the generation was ok. Then I
>> copied the product in the [plone install]/zeocluster/src directory;
>> added the helloworld lines in the [plone
>> install]/zeocluster/buildout.cfg file.
>>
>> But when I launch the buildout it says that the helloworld prduct is
>> missing the setup.py file
>>
>> And in the archgenxml product there is no setup.py file.
>>
>> Question: how can i use archgenxml to create products that can be
>> included in the plone buildout?
>>
>
> I usally create the eggs structure manually or using paster. Then I put
> the model in the 'Products' directory of the package and run and use
> ArchGenXML from there as usal.
>
> Afterwards it looks like:
>
> Products.ZZTypes/
> |-- README.txt
> |-- setup.py
> `-- src
> |-- Products
> | |-- ZZTypes
> | | |-- ZZEvent.py
> | | |-- ZZImage.py
> | | |-- ZZImageLink.py
> | | |-- __init__.py
> | | |-- config.py
> | | |-- configure.zcml
> | | |-- i18n
> | | | `-- generated.pot
> | | |-- interfaces.py
> | | |-- locales
> | | |-- profiles
> | | | `-- default
> | | | |-- ZZTypes_marker.txt
> | | | |-- cssregistry.xml
> | | | |-- factorytool.xml
> | | | |-- import_steps.xml
> | | | |-- jsregistry.xml
> | | | |-- metadata.xml
> | | | |-- skins.xml
> | | | |-- types
> | | | | |-- ZZEvent.xml
> | | | | |-- ZZImage.xml
> | | | | `-- ZZImageLink.xml
> | | | `-- types.xml
> | | |-- profiles.zcml
> | | |-- refresh.txt
> | | |-- setuphandlers.py
> | | `-- skins
> | | |-- zztypes_images
> | | | |-- ZZEvent.gif
> | | | |-- ZZEvent.gif.metadata
> | | | |-- ZZImage.gif
> | | | |-- ZZImage.gif.metadata
> | | | |-- ZZImageLink.gif
> | | | `-- ZZImageLink.gif.metadata
> | | |-- zztypes_styles
> | | `-- zztypes_templates
> | |-- __init__.py
> | |-- archgenxml.log
> | |-- zztypes.zuml
> | |-- zztypes.zuml.bak.0
> | |-- zztypes.zuml.bak.1
> | |-- zztypes.zuml.bak.2
> | |-- zztypes.zuml.bak.3
> | `-- zztypes.zuml.bak.4
> `-- Products.ZZTypes.egg-info
> ...
>
> hth
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mirtosilvio_busico.vcf
Type: text/x-vcard
Size: 284 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-product-developers/attachments/20090603/d0a4a8d4/attachment.vcf>
More information about the Product-Developers
mailing list