From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Cleber Rosa <crosa@redhat.com>
Subject: Revisiting VERSION for Python subpackage
Date: Wed, 20 Jan 2021 11:34:50 -0500 [thread overview]
Message-ID: <1360c01c-6e90-c3e7-ffc8-88adbc560ffc@redhat.com> (raw)
Hi Peter: In the past, you expressed hesitation over adding another
VERSION file to ./python/, preferring we single-source it somehow.
For now, I believe I will be pursuing a version of 0.6.0.0a1 to indicate
the subpackage is in a beta state, but otherwise tied/related to the
QEMU 6.0 release. I plan to change this to '0.6.0' during the release
candidate phase.
(It also leaves open the door to begin independent versioning schemes
later if we want to fork useful parts of the library out.)
Due to the way python packaging works, there is currently no way to
refer to files *above* the python package root because files are copied
out to a temporary, isolated environment. I do not believe there is any
way for me to avoid creating a second file.
I wanted to check and make sure this wasn't going to be a no-go.
--js
reply other threads:[~2021-01-20 16:37 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=1360c01c-6e90-c3e7-ffc8-88adbc560ffc@redhat.com \
--to=jsnow@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).