Package Details: sndio 20161106-2

Git Clone URL: (read-only)
Package Base: sndio
Description: Small audio and MIDI framework part of the OpenBSD project
Upstream URL:
Licenses: MIT
Submitter: pckbls
Maintainer: pckbls
Last Packager: pckbls
Votes: 14
Popularity: 3.898799
First Submitted: 2015-08-29 12:44
Last Updated: 2017-02-24 17:00

Latest Comments

jamesan commented on 2017-08-29 16:46

I wrapped up the changes I had just suggested in a diff file made against this package repo's latest commit so it'd be easy to pull them in:

The actual software in this package is still the same, I realise. <_<"

jamesan commented on 2017-08-29 16:31

I noticed a couple minor packaging guideline exceptions. tl;dr: nothing fatal, but also pretty trivial to address: the version string should match the version used upstream and the source package's URI should point to a versioned tarball.


The latest upstream version is 1.2.0, which should be reflected in the $pkgver.

The ISO 8601 format, i.e. the YYYYMMDD like what's in use now 20161106, should be used as the date this version of the PKGBUILD is published as a last resort when no clear version mechanism is found. This satisfies the need for versioning to always be monotonically increasing (as dates only increment with time).


The source URI of the package points to a dev snapshot. tl;dr -- change the URI to: and all is good.

Guideline indicates packages must provide stable release software unless suffixed with something indicating it's of a dev/debug/unstable nature like many packages do by suffixing their names with the VCS used to manage the dev code line, e.g. sndio-git. The "-nightly" suffix seems well accepted for non-VCS unstable packages derived from a series of regular (e.g. nightly) tarball snapshots. The "-dev" and "-devel" suffixes are falling out of use in favour of the VCS ones.

In this case, it's just a technicality as the stable release and development snapshot tarballs have identical contents as shown by running a recursive diff over the two packages that indicates zero difference. The only risk is that the non-versioned URI may contain changed code in the future (which would fail the source file integrity check) as it probably is meant to always point to the latest dev snapshot, while the versioned URI will always return the same version of this software indefinitely.

evorster commented on 2017-08-09 12:37

Hi there.

sndio installation is causing shadow.service to fail.

Aug 09 00:00:56 Vorster.Home systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Aug 09 00:00:56 Vorster.Home systemd[1]: shadow.service: Unit entered failed state.
Aug 09 00:00:56 Vorster.Home sh[3382]: user 'sndiod': directory '/var/lib/sndiod' does not exist

I checked, there is indeed no /var/lib/sndiod
When the package installs it should check for the existince of this directory, and create it if it is not present

escondida commented on 2017-03-08 18:57

Perhaps I'm missing something, but when I run sndiod and configure (say) mpv and mpd to use it, it always seems to claim the soundcard completely for one program. How do you get it to play nicely with multiple inputs?

pckbls commented on 2017-02-24 17:00

Thanks for the suggestion. Fixed.

reverendpain commented on 2017-02-24 16:56

Remove $pkgname from the PKGBUILD lines 20 and 26. It is unnecessary and causes the build to fail.