Hi,

On Fri, 03.07.2009 at 13:30:44 +0000, Maurits van Rees 
<[email protected]> wrote:
> Toni Mueller, on 2009-06-29:
> > 1. I failed to package the product as an egg. Fiddling with SOURCES.txt
> >    and MANIFEST.txt and MANIFEST.in didn't help. I ended up publishing
> >    the product as a tarball, using a hand-crafted SOURCES.txt. But the
> >    product seems to be a little unwieldy to install.
> 
> Fiddling with MANIFEST.in might help;

I tried it in both the product's "root", as well in the .egg-info
subdirectory, but to no avail.

> the other files you mention are generated automatically by the
> setup.py.  Is the product in subversion?

No. The code is in my private (= not accessible from the Internet)
bazaar repository. In the meantime, I was pointed to a bazaar plugin
for setuptools, but could not get that to run.

> If you try to create an egg from an svn *export* this will likely
> miss several files.  You should create it from a svn *checkout*.

I tried to create it from the working tree and had setup.cfg modified
to not mention svn anymore.

> Which product is it?

on.sales

> What is the location of the source code?

The code is on PYPI.

> I personally use (and have partly built) zest.releaser to do releases.
> Without any extra packages to help you the following should normally
> work, assuming you are using subversion:
> 
> svn co <url to the source code, preferrably a tag>
> cd into that directory
> python2.4 setup.py register # to register at pypi, or to update the info
> python2.4 setup.py sdist upload # upload a source dist to pypi

Well, these steps didn't produce the desired results, but the broken
egg instead.

> The homepage of your product on plone.org should have a link somewhere
> (perhaps just the 'add item' drop down menu) to add a Poi Issue
> Tracker.

Thanks, someone mentioned that to me, too.

> It might also be buried somewhere in the edit form of the
> project.

Yes. Me thinks that the Plone software center is an unwieldy product
for the uninitiated.

> If you do not see it: try it via http://old.plone.org.  That
> is the same zope instance as plone.org, just with the old skin; same
> username/password to login.

Btw, the old skin was generally much easier to work with, imho.


Kind regards,
--Toni++


_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers

Reply via email to