On 2023/01/05 15:31, SASANO Takayoshi wrote: > Hi, > > > Unless installed in a way to make it hard to pick up accidentally (e.g. > > a non-standard directory, which has its own problems) I expect the > > amount of work needed to cope with this in the rest of the ports tree > > is likely to be quite a lot more than that needed to port a couple of > > applications from alsa to sndio. > > That's important. OpenBSD's standard is sndio, not alsa. > I expected this alsa port to use temporary, for example; > > - until the application supports sndio > - rescue that cannot support sndio > > So alsa should not be first choice on OpenBSD. > > How about to use PERMIT_PACKAGE=No (and PERMIT_DISTFILES=No?) to > reduce install accidentaly, and install alsa suites into > /usr/local/alsa or somewhere?
Assuming you're wanting to add a port/package for MSHV which would depend on alsa, PERMIT_PACKAGE=No doesn't help, the alsa packages will still be built and installed when required as a dependency on bulk build machines. A non-standard directory would help, but not one which is likely to appear in search paths - I would think some software might look under /usr/local/alsa. The most common method to deal with this in ports is to continue to use /usr/local but install under subdirectories with a non-standard prefix, often 'e'; for example libraries under /usr/local/lib/ealsa and headers under /usr/local/include/ealsa. pkg-config files need to stay under /usr/local/lib/pkgconfig but the filenames can have a prefix instead so the usual pkg-config checks won't find them unless they're patched.
