From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: cygport depends: python3 over detection ?
Date: Fri, 20 May 2016 14:26:00 -0000 [thread overview]
Message-ID: <9d087151-aad6-c4c3-5d46-4f008fc4f422@gmail.com> (raw)
Hi Yaakov,
I have the impression that cygport is
reporting python3 dependency also when just
python is enough.
On lilypond, I seen only Python 2.7 dependencies
or generic ones:
$ file usr/share/lilypond/2.19.42/python/*
usr/share/lilypond/2.19.42/python/book_base.py: Python script,
ASCII text executable
usr/share/lilypond/2.19.42/python/book_base.pyc: python 2.7
byte-compiled
usr/share/lilypond/2.19.42/python/book_docbook.py: Python script,
ASCII text executable
usr/share/lilypond/2.19.42/python/book_docbook.pyc: python 2.7
byte-compiled
...
usr/share/lilypond/2.19.42/python/musicxml.py: Python script,
UTF-8 Unicode text executable
usr/share/lilypond/2.19.42/python/musicxml.pyc: python 2.7
byte-compiled
usr/share/lilypond/2.19.42/python/rational.py: Python script,
ASCII text executable
usr/share/lilypond/2.19.42/python/rational.pyc: python 2.7
byte-compiled
usr/share/lilypond/2.19.42/python/safeeval.py: Python script,
ASCII text executable
usr/share/lilypond/2.19.42/python/safeeval.pyc: python 2.7
byte-compiled
I don't see anything that specifically requires python3.
I uploaded here
http://matzeri.altervista.org/works/cygport/
the log of
$ cygport --debug lilypond.cygport depends |& tee depends.log
and here the packages:
http://matzeri.altervista.org/x86_64/lilypond/
(I removed python3 from setup.hint manually)
Regards
Marco
--
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
reply other threads:[~2016-05-20 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d087151-aad6-c4c3-5d46-4f008fc4f422@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).