Github messages for voidlinux
 help / color / mirror / Atom feed
From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: pleroma-2.4.3
Date: Tue, 02 Aug 2022 15:00:46 +0200	[thread overview]
Message-ID: <20220802130046.zYwm1YFeCxmWFbU8DUcuSVmTcSkBx5eSnKgLtaw-zVc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35539@inbox.vuxu.org>

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

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

New package: pleroma-2.4.3
https://github.com/void-linux/void-packages/pull/35539

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

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


#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**


<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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
-->

I've been running this successfully on my x86_64-glibc server, and just tested it briefly on armv7l-glibc (rpi2) and it worked great. 

This does require a PostgreSQL installation with the `postgresql*-contrib` package for it's version, but not a specific version, so I didn't want to enforce a specific version by putting it in depends.

I patched the release to not include ERTS and instead use the ERTS included in the `erlang` package, which is one way to deal with cross-builds. Another would be (I think) instead of patching it as `include_erts: false`, just do `include_erts: /${XBPS_CROSS_BASE}/usr/lib/erlang/erts-*` or something similar depending on whether it's a cross-build or not.

For the licenses, I included every license mentioned in COPYING. If this is too much, I think it would be possible to remove some of the assets without too much work.

      parent reply	other threads:[~2022-08-02 13:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 19:14 [PR PATCH] New package: pleroma-2.4.2 TinfoilSubmarine
2022-02-12 22:55 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-02-12 22:57 ` TinfoilSubmarine
2022-02-12 23:05 ` [WIP] " TinfoilSubmarine
2022-02-14 14:39 ` TinfoilSubmarine
2022-02-14 14:44 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-02-14 15:19 ` TinfoilSubmarine
2022-02-15 18:45 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-02-16 21:45 ` [PR REVIEW] " notthewave
2022-02-16 22:04 ` TinfoilSubmarine
2022-02-16 22:05 ` notthewave
2022-04-20 18:29 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-04-21 12:38 ` TinfoilSubmarine
2022-04-21 12:58 ` TinfoilSubmarine
2022-05-06 12:01 ` TinfoilSubmarine
2022-08-02 13:00 ` New package: pleroma-2.4.3 TinfoilSubmarine
2022-08-02 13:00 ` TinfoilSubmarine [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=20220802130046.zYwm1YFeCxmWFbU8DUcuSVmTcSkBx5eSnKgLtaw-zVc@z \
    --to=tinfoilsubmarine@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).