On Sat, Jan 07, 2023 at 12:39:00PM +0000, Stuart Henderson wrote: > On 2023/01/07 13:25, Antoine Jacoutot wrote: > > On Sat, Jan 07, 2023 at 08:11:22PM +0900, SASANO Takayoshi wrote: > > > Hello, > > > > > > alsa-lib.tgz (take3) attached. > > > > > > > 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. > > > > > > Many code uses <alsa/foobar.h> so putting include files to > > > /usr/<somewhere>/include/ealsa is hard to use. > > > > > > I show my idea via attached archive, almost all alsa components are > > > installed into /usr/local/ealsa. > > > > I really find this weird. > > We only do this "e" stuff for things we have in base already (like openssl). > > For stuff that we want to keep "hidden" we usually just install in a > > subdir, > > like libinotify, heimdal etc. > > If you have a good idea that is unlikely to be picked up then yes. > I don't particularly want to look into 100-odd ports to find a "safe" > directory name for that though ;)
Let's keep it simple like: /usr/local/lib/alsa-lib/... /usr/local/include/alsa-lib/... -- Antoine
