Github messages for voidlinux
 help / color / mirror / Atom feed
From: Karlson2k <Karlson2k@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libmicrohttpd: remove unused dependencies, fix
Date: Wed, 31 May 2023 15:45:24 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44191@inbox.vuxu.org> (raw)

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

There is a new pull request by Karlson2k against master on the void-packages repository

https://github.com/Karlson2k/void-packages libmicrohttpd_fix_03
https://github.com/void-linux/void-packages/pull/44191

libmicrohttpd: remove unused dependencies, fix
A few simplification for libmicrohttpd:
* Removed unneeded `--enable-largefile`. This is detected automatically by `configure`.
* Removed unneeded `gettext` dependency. It was needed for one broken tarball in the past (the timestamp was wrong resulting in documentation useless rebuild). Current tarballs have no problem with timestamps.
* Removed unneeded `libgcrypt` dependency. It was needed for ten years old GnuTLS versions for proper initialisaion.
* Fixed `changelog` URL. Some releases are made not with `master` branch, which content is returned by default. Releases are always tagged so the link should be always valid and actual.

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

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

From 240e48b545224436b5898b4e269c9b4bc3137abc Mon Sep 17 00:00:00 2001
From: "Evgeny Grin (Karlson2k)" <k2k@narod.ru>
Date: Wed, 31 May 2023 16:09:44 +0300
Subject: [PATCH] libmicrohttpd: remove unused dependencies, fix

---
 srcpkgs/libmicrohttpd/template | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/libmicrohttpd/template b/srcpkgs/libmicrohttpd/template
index 3764646cec11..6d2c8b414779 100644
--- a/srcpkgs/libmicrohttpd/template
+++ b/srcpkgs/libmicrohttpd/template
@@ -1,20 +1,18 @@
 # Template file for 'libmicrohttpd'
 pkgname=libmicrohttpd
 version=0.9.77
-revision=1
+revision=2
 build_style=gnu-configure
 configure_args="
- --enable-largefile
  --enable-https
  --enable-messages"
-hostmakedepends="texinfo"
-makedepends="libgcrypt-devel gnutls-devel"
+makedepends="gnutls-devel"
 checkdepends="libcurl-devel"
 short_desc="Library embedding HTTP server functionality"
 maintainer="Duncaen <duncaen@voidlinux.org>"
 license="LGPL-2.1-or-later"
 homepage="https://www.gnu.org/software/libmicrohttpd/"
-changelog="https://git.gnunet.org/libmicrohttpd.git/plain/ChangeLog"
+changelog="https://git.gnunet.org/libmicrohttpd.git/tree/ChangeLog?h=v${version}"
 distfiles="${GNU_SITE}/libmicrohttpd/libmicrohttpd-${version}.tar.gz"
 checksum=9e7023a151120060d2806a6ea4c13ca9933ece4eacfc5c9464d20edddb76b0a0
 

             reply	other threads:[~2023-05-31 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 13:45 Karlson2k [this message]
2023-05-31 20:31 ` [PR PATCH] [Closed]: " Duncaen

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-44191@inbox.vuxu.org \
    --to=karlson2k@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).