Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] enchant2: update to 2.6.3.
Date: Sat, 16 Dec 2023 18:30:48 +0100	[thread overview]
Message-ID: <20231216173048.VR-NW5v1prXhX9n4CgH84jMrE1Slto8wMhyMwIgq18g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47698@inbox.vuxu.org>

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

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

https://github.com/mhmdanas/void-packages enchant2-2.6.3
https://github.com/void-linux/void-packages/pull/47698

enchant2: update to 2.6.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

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

<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


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

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

From 3a04e90edd2698c2a97fb75ee96b1cf932b4d335 Mon Sep 17 00:00:00 2001
From: Mohammed Anas <triallax@tutanota.com>
Date: Mon, 11 Dec 2023 20:54:00 +0000
Subject: [PATCH] enchant2: update to 2.6.4.

---
 srcpkgs/enchant2/template | 11 ++---------
 1 file changed, 2 insertions(+), 9 deletions(-)

diff --git a/srcpkgs/enchant2/template b/srcpkgs/enchant2/template
index 6ba1e36cdf8e1..8055c1c7bb395 100644
--- a/srcpkgs/enchant2/template
+++ b/srcpkgs/enchant2/template
@@ -1,15 +1,8 @@
 # Template file for 'enchant2'
 pkgname=enchant2
-version=2.6.1
+version=2.6.4
 revision=1
 build_style=gnu-configure
-# so package doesn't conflict with enchant's /usr/share/enchant/enchant.ordering;
-# might be a bug in their build system that only this directory and/or file aren't
-# suffixed appropriately.
-# passing this in make is safe because this is the value used to define the macro
-# that their code uses to find enchant.ordering
-make_build_args="pkgdatadir=/usr/share/enchant-2"
-make_install_args="$make_build_args"
 # tests need --enable-relocatable
 configure_args="--enable-relocatable"
 hostmakedepends="pkg-config groff"
@@ -22,7 +15,7 @@ license="LGPL-2.1-or-later"
 homepage="https://abiword.github.io/enchant/"
 changelog="https://raw.githubusercontent.com/AbiWord/enchant/master/NEWS"
 distfiles="https://github.com/AbiWord/enchant/releases/download/v${version}/enchant-${version}.tar.gz"
-checksum=f24e12469137ae1d03140bb9032a47a5947c36f4d1e2f12b929061005eb15279
+checksum=833b4d5600dbe9ac867e543aac6a7a40ad145351495ca41223d4499d3ddbbd2c
 make_check=no # tests broken
 
 enchant2-devel_package() {

  reply	other threads:[~2023-12-16 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 20:54 [PR PATCH] " mhmdanas
2023-12-16 17:30 ` mhmdanas [this message]
2024-02-14 11:02 ` [PR PATCH] [Closed]: enchant2: update to 2.6.4 mhmdanas
2024-02-14 17:07 ` leahneukirchen

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=20231216173048.VR-NW5v1prXhX9n4CgH84jMrE1Slto8wMhyMwIgq18g@z \
    --to=mhmdanas@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).