Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] perl: depends on libxcrypt-devel
Date: Fri, 29 Dec 2023 16:38:44 +0100	[thread overview]
Message-ID: <20231229153844.iI_ZDio4Q6WP3NoPJficokTzcK4zZWVp3y-4vAHJHhs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47979@inbox.vuxu.org>

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

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

https://github.com/oreo639/void-packages perl
https://github.com/void-linux/void-packages/pull/47979

perl: depends on libxcrypt-devel
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

Fixes https://github.com/void-linux/void-packages/pull/47977

<!--
#### 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/47979.patch is attached

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

From 0bd08aa90e78515eb759ae94cde9f08685dc29ec Mon Sep 17 00:00:00 2001
From: oreo639 <oreo6391@gmail.com>
Date: Fri, 29 Dec 2023 07:27:21 -0800
Subject: [PATCH] perl: depends on libxcrypt-devel

When crypt support is enabled, the public header files also includes
crypt.h in core_perl/CORE/reentr.h
---
 srcpkgs/perl/template | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/perl/template b/srcpkgs/perl/template
index b82da36b50f06..010bda8cd3f98 100644
--- a/srcpkgs/perl/template
+++ b/srcpkgs/perl/template
@@ -1,7 +1,7 @@
 # Template file for 'perl'
 pkgname=perl
 version=5.38.2
-revision=2
+revision=3
 _perl_cross_version=1.5.2
 build_style=gnu-configure
 makedepends="zlib-devel bzip2-devel gdbm-devel db-devel"
@@ -20,6 +20,7 @@ skip_extraction=perl-cross-${_perl_cross_version}.tar.gz
 
 if [ "$XBPS_TARGET_LIBC" = "glibc" ]; then
 	makedepends+=" libxcrypt-devel"
+	depends+=" libxcrypt-devel"
 fi
 
 # Before updating this package to a new major version, run

  reply	other threads:[~2023-12-29 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29 15:33 [PR PATCH] " oreo639
2023-12-29 15:38 ` oreo639 [this message]
2023-12-29 16:22 ` oreo639
2023-12-29 16:26 ` tsndqst
2023-12-31 14:33 ` [PR PATCH] [Merged]: " 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=20231229153844.iI_ZDio4Q6WP3NoPJficokTzcK4zZWVp3y-4vAHJHhs@z \
    --to=oreo639@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).