Any chance you could implement that in setup.py too?
Tom
Shawn Walker wrote:
2008/5/21 Stephen Hahn <[EMAIL PROTECTED]>:
* Tom Mueller <[EMAIL PROTECTED]> [2008-05-21 19:48]:
Stephen,
The python UUID module[1] is a separate deliverable in 2.3 and 2.4 (it's
included with python in 2.5). It's distributed under the Python software
license.
Assuming it's ok to bring that dependency in, should this be in a separate
package (like cherrypy)? It's only a single file (uuid.py). If not, would
it just be dropped in /usr/lib/python2.4/vendor-packages?
Is there any expectation of moving to python 2.5 for other reasons soon?
No, I don't think so.
srce/modules/Queue25.py is also from 2.5. Just pull in uuid as
Uuid25.py and deliver it as part of SUNWipkg. My expectation is that
lots of people will find CherryPy useful, and that we'll need to
update it separately.
Which reminds me... Shawn, could you see if you could keep the actual
tar file out of the repository, and pull it from some known URL as
part of the build?
I can easily do that, but I assumed that this could / would be built
on systems without access to an external location.
As such, I'll change it to:
* Check to see if the tarball exists in the pkgdef directory for CherryPy
* If it doesn't, attempt to fetch it automatically
* Failing that, abort the build and let the user know what they need to do
How does that sound?
Cheers,
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
