Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Eliminate libupnp dependencies
Date: Tue, 12 Jan 2021 05:17:46 +0100	[thread overview]
Message-ID: <20210112041746.YV3inFNf0VWRYdWqH7T74mQateq42AP0WxQ7Jx14ltA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27829@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

Eliminate libupnp dependencies
https://github.com/void-linux/void-packages/pull/27829

Description:
`djmount` is ancient (from 2006) and, after the initial packaging, has only ever been revbumped to rebuild for dependency updates. It refuses to build against `libupnp1.8` or newer and is holding back our `libupnp`.

`retroshare` has some upstream patches to build against `libupnp1.8` but they do not apply cleanly to the release version. However, the package builds against `miniupnpc`, so let's do that. We can revisit newer `libupnp` later if there is a compelling reason and they cut a new release.

This paves the way for updating `libupnp` to a modern version. Maybe we can unify the `libupnp` if we can clean up `gerbera`, `mpd` and `vlc`. If not, maybe `libupnp` should be a meta that pulls in the latest versioned package.

      parent reply	other threads:[~2021-01-12  4:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 16:58 [PR PATCH] " ahesford
2021-01-11 17:07 ` [PR PATCH] [Updated] " ahesford
2021-01-12  4:17 ` ahesford [this message]

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=20210112041746.YV3inFNf0VWRYdWqH7T74mQateq42AP0WxQ7Jx14ltA@z \
    --to=ahesford@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).