[Bug 717966] Review Request: python-psphere - vSphere SDK for Python
bugzilla at redhat.com
bugzilla at redhat.com
Tue Jul 12 17:24:03 UTC 2011
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=717966
--- Comment #10 from Chris Lalancette <clalance at redhat.com> 2011-07-12 13:24:02 EDT ---
(In reply to comment #8)
> > %{!?python_sitelib: %global python_sitelib %(python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")}
>
> Not needed anymore:
>
> http://fedoraproject.org/wiki/Packaging:Python#Macros
Ah, I had no idea about that one. Fixed.
>
> > %dir %attr(0755, root, root) %{python_sitelib}/psphere
> > %{python_sitelib}/psphere/*
>
> A simple:
>
> %{python_sitelib}/psphere/
And fixed.
(In reply to comment #9)
> (In reply to comment #7)
> > (In reply to comment #3)
> > > - There is no 0.1 release of psphere yet, so we should either wait for a
> > > release or (uggh) get into:
> > >
> > >
> > > http://fedoraproject.org/wiki/Packaging:NamingGuidelines#NonNumericRelease
> >
> > This is the nastiest one here. When you run "python setup.py sdist" on the hg
> > sources, you get a tarball out that is named "psphere-0.1.tar.gz". Given the
> > "Referencing_Source" link below, I feel like we should stick with that version
> > number, even though there is no official upstream release.
>
> Nope, that doesn't cut it - upstream could release 0.1 some time in the future
> with newer code
>
> 0.1 as a version number is meaningless right now - it doesn't refer to a
> specific version of the code
>
> It sounds like you're in good contact with upstream - how about suggesting a
> release? That might be the simplest way of resolving it?
>
> Otherwise, it should be python-vsphere-0.1-0.1.42accc3ffe67hg
I've written to the upstream maintainer, I'll wait on his reply.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the package-review
mailing list