Creating a binary install package when target python version is unknown

[Michael Verrilli <msv at pobox dot com>]

I was looking to create a binary install package for newt, however it
looks like the binary installs are extracted to root.  If I have
python2.7 installed, there are different binaries and install
locations (and bootstrap .py) than python3, for example.

Does this mean I have to install all combinations? Or is there some
special way to do this that I am missing?  When I make it from source,
the makefile will detect which versions of python are installed and
compile appropriately.

Also, how do I know which versions of python I should be building for?

As an example, here are the files that would be installed for python2.7:

./usr/lib/python2.7/site-packages/snack.py
./usr/lib/python2.7/site-packages/_snack.py
./usr/lib/python2.7/site-packages/_snackmodule.so

and python3 would have its own set.

How is this usually handled?

Thanks!

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple