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] [Merged]: pdfpc: disable REST server
Date: Wed, 10 Apr 2024 00:36:17 +0200	[thread overview]
Message-ID: <20240409223617.D651E23E12@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48959@inbox.vuxu.org>

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

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

pdfpc: disable REST server
https://github.com/void-linux/void-packages/pull/48959

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

Build with webkit2gtk-4.1, which provides an identical api to webkit2gtk-4.0 except it uses libsoup3.
The REST server functionality requires libsoup2. libsoup2 and libsoup3 cannot be loaded in the same process at the same time.

One of the maintainers recommended just disabling the rest server and building the markdown presentation notes viewer with webkit2gtk-4.1 stating that as far as he knows, he is the only one that actually uses the rest server function. https://github.com/pdfpc/pdfpc/issues/671#issuecomment-1552713117

I was wondering if anyone here that uses pdfpc uses the rest server function?

<!--
#### 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
-->


      parent reply	other threads:[~2024-04-09 22:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27  0:35 [PR PATCH] " oreo639
2024-02-27 14:51 ` leahneukirchen
2024-02-27 20:31 ` oreo639
2024-02-27 20:31 ` oreo639
2024-02-27 20:39 ` [PR PATCH] [Updated] " oreo639
2024-02-29 10:26 ` sgn
2024-02-29 21:04 ` [PR PATCH] [Updated] " oreo639
2024-02-29 21:08 ` oreo639
2024-04-09 22:36 ` oreo639 [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=20240409223617.D651E23E12@inbox.vuxu.org \
    --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).