From: "Michael Haubenwallner" <haubi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/parity/
Date: Wed, 23 Oct 2019 07:28:10 +0000 (UTC) [thread overview]
Message-ID: <1571815665.24fd4083365080da583bc9b85a8f306369a6a331.haubi@gentoo> (raw)
commit: 24fd4083365080da583bc9b85a8f306369a6a331
Author: Michael Haubenwallner <haubi <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 23 07:23:02 2019 +0000
Commit: Michael Haubenwallner <haubi <AT> gentoo <DOT> org>
CommitDate: Wed Oct 23 07:27:45 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=24fd4083
sys-devel/parity: no minor version since VS 2017 (vc15)
Updating Microsoft Visual Studio since 2017 may bump minor version
number, but we don't want another CHOST vendor value for that.
Package-Manager: Portage-2.3.69, Repoman-2.3.16
Signed-off-by: Michael Haubenwallner <haubi <AT> gentoo.org>
sys-devel/parity/metadata.xml | 4 ++--
sys-devel/parity/parity-9999.ebuild | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/sys-devel/parity/metadata.xml b/sys-devel/parity/metadata.xml
index b5ae82a3cc8..40c8b82ed8b 100644
--- a/sys-devel/parity/metadata.xml
+++ b/sys-devel/parity/metadata.xml
@@ -17,8 +17,8 @@
<flag name="vc11_0">Enable support for Visual Studio 2012</flag>
<flag name="vc12_0">Enable support for Visual Studio 2013</flag>
<flag name="vc14_0">Enable support for Visual Studio 2015</flag>
- <flag name="vc15_0">Enable support for Visual Studio 2017</flag>
- <flag name="vc16_2">Enable support for Visual Studio 2019</flag>
+ <flag name="vc15">Enable support for Visual Studio 2017</flag>
+ <flag name="vc16">Enable support for Visual Studio 2019</flag>
<flag name="vc_x64">Enable support for 64bit Visual Studio compilers</flag>
<flag name="vc_x86">Enable support for 32bit Visual Studio compilers</flag>
</use>
diff --git a/sys-devel/parity/parity-9999.ebuild b/sys-devel/parity/parity-9999.ebuild
index 50ab4b1e491..f1ec325bab1 100644
--- a/sys-devel/parity/parity-9999.ebuild
+++ b/sys-devel/parity/parity-9999.ebuild
@@ -16,7 +16,7 @@ HOMEPAGE="https://github.com/haubi/parity"
parity-vcarchs() { echo x64 x86 ; }
parity-vcvers-legacy() { echo 7_0 7_1 8_0 9_0 ; }
-parity-vcvers-current() { echo 10_0 11_0 12_0 14_0 15_0 16_2 ; }
+parity-vcvers-current() { echo 10_0 11_0 12_0 14_0 15 16 ; }
parity-vcvers() {
parity-vcvers-legacy
parity-vcvers-current
next reply other threads:[~2019-10-23 7:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 7:28 Michael Haubenwallner [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-24 13:09 [gentoo-commits] repo/gentoo:master commit in: sys-devel/parity/ Andrew Ammerlaan
2022-06-24 13:09 Andrew Ammerlaan
2021-04-23 6:53 Michael Haubenwallner
2020-03-12 6:55 Michael Haubenwallner
2020-03-11 8:11 Michael Haubenwallner
2020-03-11 8:11 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2019-08-23 14:57 Michael Haubenwallner
2019-08-12 13:05 Michael Haubenwallner
2019-06-17 8:57 Michael Haubenwallner
2018-07-03 14:36 Michael Haubenwallner
2018-05-16 13:09 Michael Haubenwallner
2017-05-03 15:25 Michael Haubenwallner
2017-04-01 13:04 Michael Haubenwallner
2017-03-23 8:52 Michael Haubenwallner
2017-01-29 20:14 Fabian Groffen
2016-10-30 20:05 Sven Wegener
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=1571815665.24fd4083365080da583bc9b85a8f306369a6a331.haubi@gentoo \
--to=haubi@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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