Skip to content

swayimg: update to 5.1.#59748

Open
voidbert wants to merge 1 commit intovoid-linux:masterfrom
voidbert:swayimg
Open

swayimg: update to 5.1.#59748
voidbert wants to merge 1 commit intovoid-linux:masterfrom
voidbert:swayimg

Conversation

@voidbert
Copy link
Copy Markdown
Contributor

@voidbert voidbert commented Apr 4, 2026

Updates swayimg (new Lua configuration files are required) and adds support for new image formats.

Testing the changes

  • I tested the changes in this PR: YES

I have confirmed all files required by CONFIG.md are present (see #59385):

  • /etc/xdg/swayimg/init.lua
  • /usr/share/swayimg/example.lua
  • /usr/share/swayimg/swayimg.lua

Local build testing

  • I built this PR locally for my native architecture, (x86_64-musl)
  • I built this PR locally for these architectures (if supported. mark crossbuilds):
    • armv6l-musl

Comment on lines +29 to +30
vmkdir etc/xdg/swayimg
cp extra/example.lua ${DESTDIR}/etc/xdg/swayimg/init.lua
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
vmkdir etc/xdg/swayimg
cp extra/example.lua ${DESTDIR}/etc/xdg/swayimg/init.lua
vinstall extra/example.lua 0644 etc/xdg/swayimg init.lua

Copy link
Copy Markdown
Contributor

@dogknowsnx dogknowsnx Apr 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just gave a quick example in the other PR, vinstall should suffice here (better wait for member input)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried vconf as well (to avoid the conf_files declaration) but that doesn't create the parent directories. vinstall seems the best option to me (with my limited xbps knowledge).

@voidbert voidbert requested a review from dogknowsnx April 5, 2026 20:32
@dogknowsnx
Copy link
Copy Markdown
Contributor

dogknowsnx commented Apr 5, 2026

I tried vconf as well (to avoid the conf_files declaration) but that doesn't create the parent directories. vinstall seems the best option to me (with my limited xbps knowledge).

That still leaves us w/ the other two example.lua files (see my other comment) - again, it's for the person doing the merging to decide whether they want to keep any of those files, or if they prefer to not install anything into etc and let the user figure it out by referring to the *.md files (personally, I'd just keep /etc/xdg/swayimg/init.lua and be done w/ it)

@voidbert
Copy link
Copy Markdown
Contributor Author

voidbert commented Apr 5, 2026

I'm in favor of keeping both copies of example.lua. Yes, it's redundant, but it's in accordance with swayimg's CONFIG.md instructions. In case a user follows them, there won't be any missing files.

I believe more problems will arise from a poor transition between the old and new configuration files, as support for old configs was completely removed without prior warning.

@dogknowsnx
Copy link
Copy Markdown
Contributor

dogknowsnx commented Apr 5, 2026

My point is, that w/ the proposed changes to the template the following identical (content-related) files will be installed

/usr/share/swayimg/example.lua # by upstream
/usr/share/examples/swayimg/example.lua # by 'vsconf'
/etc/xdg/swayimg/init.lua # by 'vinstall'

where the second is arguably the most redundant (for not being mentioned in the docs)

Regarding the transition to the new lua-based configuration, consider adding an INSTALL.msg (please wait for a member to step in)

@voidbert
Copy link
Copy Markdown
Contributor Author

voidbert commented Apr 5, 2026

Yeah, you're right, I misread /usr/share/swayimg/example.lua as /usr/share/examples/swayimg/example.lua, my bad. I can fix it tomorrow morning (UTC+1). Regarding INSTALL.msg, yes, let's wait for a repo maintainer to give their opinion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants