Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: libreoffice: update to 7.1.3.2, adopt.
Date: Wed, 12 May 2021 05:03:05 +0200	[thread overview]
Message-ID: <20210512030305.nIjNGGZiaL_smtaGBd28bQAj8GbXR6sjzOVgVI5JP5g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30793@inbox.vuxu.org>

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

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

libreoffice: update to 7.1.3.2, adopt.
https://github.com/void-linux/void-packages/pull/30793

Description:
- remove comment about missing dependencies: they are either not used by
  the current configuration (krb5 with system postgresql or nasm with
  system libjpeg) or were made to be used in this update (poppler)
- use system fontforge to build opens___.ttf
- use system ucpp as preprocessor
- use system python3-lxml in the build process
- use system poppler and libxml2
- remove outdated libtommath from distfiles
- use vsed everywhere (and remove outdated stuff)
- be explicit about bundling fonts
- use make_build_target instead of make_build_args (more semantically correct)

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

I'd like to merge #30789 first

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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
-->

[ci skip]

      parent reply	other threads:[~2021-05-12  3:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11  5:44 [PR PATCH] " ericonr
2021-05-11  5:46 ` [PR REVIEW] " heliocat
2021-05-11  5:51 ` [PR PATCH] [Updated] " ericonr
2021-05-11  5:55 ` ericonr
2021-05-11 13:50 ` ericonr
2021-05-11 15:49 ` ericonr
2021-05-12  3:03 ` ericonr [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=20210512030305.nIjNGGZiaL_smtaGBd28bQAj8GbXR6sjzOVgVI5JP5g@z \
    --to=ericonr@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).