From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] [WIP] occt: update to 7.4.0.
Date: Sat, 05 Oct 2019 01:49:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15102@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
There is a new pull request by Piraty against master on the void-packages repository
https://github.com/Piraty/void-packages occt-7.4.0
https://github.com/void-linux/void-packages/pull/15102
[WIP] occt: update to 7.4.0.
Tracking PR.
- [ ] actually build the hole thing locally for all relevant archs
- [ ] check what freecad says about it
- [ ] test the musl patches (someone?)
@karl-nilsson @yopito
A patch file from https://github.com/void-linux/void-packages/pull/15102.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-occt-7.4.0-15102.patch --]
[-- Type: text/x-diff, Size: 1524 bytes --]
From 5be5b6cc9ad3fe88121a9e68303195d823c78e56 Mon Sep 17 00:00:00 2001
From: Piraty <piraty1@inbox.ru>
Date: Sat, 5 Oct 2019 01:19:47 +0200
Subject: [PATCH] WIP: occt: update to 7.4.0.
[ci skip]
TODO:
* actually build the hole thing
* check what freecad says about it
* test the musl patches
---
srcpkgs/occt/{patches => }/musl-fenv.patch | 0
srcpkgs/occt/template | 4 ++--
2 files changed, 2 insertions(+), 2 deletions(-)
rename srcpkgs/occt/{patches => }/musl-fenv.patch (100%)
diff --git a/srcpkgs/occt/patches/musl-fenv.patch b/srcpkgs/occt/musl-fenv.patch
similarity index 100%
rename from srcpkgs/occt/patches/musl-fenv.patch
rename to srcpkgs/occt/musl-fenv.patch
diff --git a/srcpkgs/occt/template b/srcpkgs/occt/template
index 70647369464..794f88a298a 100644
--- a/srcpkgs/occt/template
+++ b/srcpkgs/occt/template
@@ -1,6 +1,6 @@
# Template file for 'occt'
pkgname=occt
-version=7.3.0p3
+version=7.4.0
revision=1
_gittag="V${version//./_}"
wrksrc=occt-${_gittag}
@@ -16,7 +16,7 @@ homepage="https://www.opencascade.com"
# distifile: use git instead of official tarball that requires registration
# see https://www.opencascade.com/content/packaging-again-debian
distfiles="https://git.dev.opencascade.org/gitweb/?p=occt.git;a=snapshot;h=refs/tags/${_gittag};sf=tgz>occt-${_gittag}.tar.gz"
-checksum=fbd46db3e75313131b88a606024ea4d4496c3c7f6e68c23988e9d3e673d4f21b
+checksum=655da7717dac3460a22a6a7ee68860c1da56da2fec9c380d8ac0ac0349d67676
conflicts="oce>=0"
post_install() {
next reply other threads:[~2019-10-04 23:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 23:49 voidlinux-github [this message]
2019-10-05 16:45 ` voidlinux-github
2019-10-10 15:56 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-10 15:56 ` voidlinux-github
2019-10-10 16:03 ` voidlinux-github
2019-10-10 16:03 ` voidlinux-github
2019-10-10 16:07 ` voidlinux-github
2019-10-10 16:07 ` voidlinux-github
2019-10-10 16:42 ` voidlinux-github
2019-10-10 16:42 ` voidlinux-github
2019-10-10 18:11 ` voidlinux-github
2019-10-10 18:11 ` voidlinux-github
2019-10-10 18:50 ` voidlinux-github
2019-10-10 18:50 ` voidlinux-github
2019-10-10 18:51 ` voidlinux-github
2019-10-10 18:51 ` voidlinux-github
2019-10-15 15:41 ` voidlinux-github
2019-10-15 15:41 ` voidlinux-github
2019-10-17 10:56 ` [PR PATCH] [Closed]: " voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15102@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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).