Github messages for voidlinux
 help / color / mirror / Atom feed
From: yuriy-chumak <yuriy-chumak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] ol: update to 2.3.6.
Date: Thu, 28 Jul 2022 08:39:06 +0200	[thread overview]
Message-ID: <20220728063906.mG45z_wdWGeoMs9MLeUuvEDnadS1ohmXt3PcVwosfEQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38312@inbox.vuxu.org>

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

There is an updated pull request by yuriy-chumak against master on the void-packages repository

https://github.com/otus-lisp/void-packages ol
https://github.com/void-linux/void-packages/pull/38312

ol: update to 2.3.6.
#### Testing the changes
- I tested the changes in this PR: **YES**


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

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

From 5312c3ba4a32160bb38653e4c37229ab31e1f968 Mon Sep 17 00:00:00 2001
From: Yuriy Chumak <yuriy.chumak@mail.com>
Date: Wed, 27 Jul 2022 18:30:25 +0300
Subject: [PATCH] ol: update to 2.3.6.

---
 srcpkgs/ol/template | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/ol/template b/srcpkgs/ol/template
index 40317b4324c7..e43eb1214d17 100644
--- a/srcpkgs/ol/template
+++ b/srcpkgs/ol/template
@@ -1,6 +1,6 @@
 # Template file for 'ol'
 pkgname=ol
-version=2.3.5
+version=2.3.6
 revision=1
 build_style=gnu-makefile
 hostmakedepends="xxd"
@@ -10,9 +10,13 @@ license="LGPL-3.0-or-later, MIT"
 homepage="https://yuriy-chumak.github.io/ol/"
 changelog="https://raw.githubusercontent.com/yuriy-chumak/ol/master/doc/CHANGELOG.md"
 distfiles="https://github.com/yuriy-chumak/ol/archive/${version}.tar.gz"
-checksum=1f3da2d3b2e47f5c626bfe2727b649db3fd8f53e700dad2a984314275ee7a6ff
+checksum=5a7b8ff5eeba2db63ba8d409c6ebc3af5f9cb21d14a2ec1a279d8137298360ef
 
-CFLAGS="-lm"
+CFLAGS="-lm -DOLVM_FFI -DHAS_SOCKETS -DHAS_DLOPEN"
+
+case "$XBPS_TARGET_MACHINE" in
+	i686*|x86_64*) makedepends+=" gcc-multilib";;
+esac
 
 post_install() {
 	vlicense LICENSE

  reply	other threads:[~2022-07-28  6:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 15:31 [PR PATCH] " yuriy-chumak
2022-07-28  6:39 ` yuriy-chumak [this message]
2022-07-28  7:43 ` [PR PATCH] [Updated] " yuriy-chumak
2022-07-28 18:34 ` [PR REVIEW] " classabbyamp
2022-07-28 18:34 ` classabbyamp
2022-07-29 12:13 ` yuriy-chumak
2022-07-29 12:13 ` yuriy-chumak
2022-07-29 12:16 ` [PR PATCH] [Updated] " yuriy-chumak
2022-08-01 17:21 ` [PR REVIEW] " classabbyamp
2022-08-05 11:55 ` yuriy-chumak
2022-08-05 15:10 ` Chocimier
2022-08-05 15:13 ` Chocimier
2022-08-05 16:22 ` yuriy-chumak
2022-08-05 16:25 ` yuriy-chumak
2022-08-15 14:01 ` [PR PATCH] [Updated] " yuriy-chumak
2022-08-15 14:03 ` yuriy-chumak
2022-08-15 14:04 ` yuriy-chumak
2022-08-21 18:52 ` [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=20220728063906.mG45z_wdWGeoMs9MLeUuvEDnadS1ohmXt3PcVwosfEQ@z \
    --to=yuriy-chumak@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).