X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=RxQmM7ZykQERCWHzmV2GT2pWxx0md
	VdgdWrKAKZ69E+etgnY9ah4eDIryP+e9GFZIE0G6sj3c7MsbNvx/fKntRxL04shB
	S7d3RJ72TYIFQQvJ5A0m7CImiQz71I3z46+3kSQxwYGcwvZjJD6VzSDX9ZI3d7IO
	unNea3GMm1YOF4=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; s=default; bh=/rlm1xJV2jzyymc/lAeVdrg532E=; b=Ygz
	+CuwM0CyxmNu2J39+ifq0wMEbYjqmYTqUiC0zN4pboLlhlK4ltFf2VCNmSYBaSJ+
	TrItFLJkMUjlx2s71W8ejOx1pSmUTtG/Y6AHQgV4yqe7mOL4XA2/KI4swiPLXeBr
	N4EhgYHmYQhCU1skVqygl8y7JHwqzWRtw03EsNQU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-ob0-f171.google.com
X-Received:	by 10.182.81.197 with SMTP id c5mr2132507oby.40.1392910745384; Thu, 20 Feb 2014 07:39:05 -0800 (PST)
MIME-Version:	1.0
From:	Michael Verrilli <msv AT pobox DOT com>
Date:	Thu, 20 Feb 2014 10:38:50 -0500
Message-ID:	<CAFxjCwxqVO7kUzkpJ4wqUawk9C0j0C1FOsfhR0MKoVLVKjpd5A@mail.gmail.com>
Subject:	Creating a binary install package when target python version is unknown
To:	Cygwin List <cygwin AT cygwin DOT com>
X-IsSubscribed:	yes

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

- Raw text -