Github messages for voidlinux
 help / color / mirror / Atom feed
From: lz-coder <lz-coder@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: chrono-date-3.0.1
Date: Fri, 20 Jan 2023 08:01:10 +0100	[thread overview]
Message-ID: <20230120070110.pURnC84hiMvEnGt0mlOpvLmCV6_WkRqdh5idggQYaLE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41750@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

There is an updated pull request by lz-coder against master on the void-packages repository

https://github.com/lz-coder/void-packages chrono-date
https://github.com/void-linux/void-packages/pull/41750

New package: chrono-date-3.0.1
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (X86_64-GLIBC)


A patch file from https://github.com/void-linux/void-packages/pull/41750.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chrono-date-41750.patch --]
[-- Type: text/x-diff, Size: 2119 bytes --]

From 15f25a4f75dc00fc9074ec3222aca7c20b856bc4 Mon Sep 17 00:00:00 2001
From: lz-coder <lzcoder@proton.me>
Date: Fri, 20 Jan 2023 02:34:40 -0300
Subject: [PATCH] New package: chrono-date-3.0.1

---
 common/shlibs                |  1 +
 srcpkgs/chrono-date-devel    |  1 +
 srcpkgs/chrono-date/template | 28 ++++++++++++++++++++++++++++
 3 files changed, 30 insertions(+)
 create mode 120000 srcpkgs/chrono-date-devel
 create mode 100644 srcpkgs/chrono-date/template

diff --git a/common/shlibs b/common/shlibs
index 85c08f13a05f..6a2c8e447c28 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -4224,3 +4224,4 @@ libIlmThread-3_1.so.30 libopenexr-3.1.5_1
 libOpenEXR-3_1.so.30 libopenexr-3.1.5_1
 libOpenEXRCore-3_1.so.30 libopenexr-3.1.5_1
 libOpenEXRUtil-3_1.so.30 libopenexr-3.1.5_1
+libdate-tz.so.3 chrono-date-3.0.1_1
diff --git a/srcpkgs/chrono-date-devel b/srcpkgs/chrono-date-devel
new file mode 120000
index 000000000000..7ba11f09e6bd
--- /dev/null
+++ b/srcpkgs/chrono-date-devel
@@ -0,0 +1 @@
+chrono-date
\ No newline at end of file
diff --git a/srcpkgs/chrono-date/template b/srcpkgs/chrono-date/template
new file mode 100644
index 000000000000..8802629fd99e
--- /dev/null
+++ b/srcpkgs/chrono-date/template
@@ -0,0 +1,28 @@
+# Template file for 'chrono-date'
+pkgname=chrono-date
+version=3.0.1
+revision=1
+build_style=cmake
+configure_args="-DBUILD_SHARED_LIBS=true -DBUILD_TZ_LIB=true
+ -DUSE_SYSTEM_TZ_DB=true -DENABLE_DATE_TESTING=true"
+short_desc="Date and time library based on the C++11/14/17 <chrono> header"
+maintainer="lz-coder <lzcoder@proton.me>"
+license="MIT"
+homepage="https://howardhinnant.github.io/date/date.html"
+changelog="https://github.com/HowardHinnant/date/releases"
+distfiles="https://github.com/HowardHinnant/date/archive/v${version}.tar.gz"
+checksum=7a390f200f0ccd207e8cff6757e04817c1a0aec3e327b006b7eb451c57ee3538
+
+post_install() {
+	vlicense LICENSE.txt
+}
+
+chrono-date-devel_package() {
+	depends="${sourcepkg}>=${version}_${revision}"
+	short_desc+=" - development files"
+	pkg_install() {
+		vmove usr/include
+		vmove usr/lib/cmake
+		vmove "usr/lib/*.so"
+	}
+}

  parent reply	other threads:[~2023-01-20  7:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20  5:37 [PR PATCH] " lz-coder
2023-01-20  5:46 ` [PR PATCH] [Updated] " lz-coder
2023-01-20  6:21 ` classabbyamp
2023-01-20  7:01 ` lz-coder [this message]
2023-01-20 15:34 ` [PR PATCH] [Updated] " lz-coder
2023-01-20 15:38 ` lz-coder
2023-01-22  1:47 ` [PR REVIEW] " classabbyamp
2023-01-22  3:12 ` [PR PATCH] [Updated] " lz-coder
2023-02-07  7:46 ` [PR PATCH] [Merged]: " classabbyamp

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=20230120070110.pURnC84hiMvEnGt0mlOpvLmCV6_WkRqdh5idggQYaLE@z \
    --to=lz-coder@users.noreply.github.com \
    --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).