Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: sile: update to 0.15.9
Date: Fri, 10 Jan 2025 00:41:39 +0100	[thread overview]
Message-ID: <20250109234139.1100E21383@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53839@inbox.vuxu.org>

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

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

sile: update to 0.15.9
https://github.com/void-linux/void-packages/pull/53839

Description:
Untested bump in the blind ;-)

This includes one change from the recently approved major overhaul (see #51222). The *default* upstream options use a bundling system to wrap dozens and dozens of project Lua files and embed them into the final Rust binary. This was made the default upstream to simplify installation from source for end users that may have trouble working out their system's Lua paths and may or may not compile with the right options. That being said as the upstream developer I personally recommend *not* using this option and installing all the files directly using the package manager if possible. Since this is a system package it will have all the Lua path stuff sorted out for the end user already, and this makes it easier to use SILE. One common thing to do in a SILE based project is modify some internals by copying the distributed functions and tweaking them for some specific use case. Having the system install them as actual Lua files instead of bundled in a binary makes it just a little easier to actually do that. Hence I suggest this option for distro packages.

Otherwise this is a pretty simple version bump.

#### Testing the changes
- [ ] I tested the changes in this PR: **NO**

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


      reply	other threads:[~2025-01-09 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-04 17:59 [PR PATCH] " alerque
2025-01-09 23:41 ` Johnnynator [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=20250109234139.1100E21383@inbox.vuxu.org \
    --to=johnnynator@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).