Subject: Re: Should we install to /opt ?

From: Ariadne Conill <[email-masked]>
Date: Tue, 3 Mar 2020 06:34:37 -0500

Hello,

On Mar 3, 2020 at 5:31 AM, Rasmus Thomsen  <[email-masked]>  wrote:  

 
>  
>  Hello,
>  
>  a MR for couchdb[0] was recently created that installs to /opt/alpine since couchdb puts both architecture dependent and independent files into that directory. As of right now we usually just install to /us/lib/ (e.g. for firefox and chromium), even if the package also puts architecture independent data into that directory. Should we adhere to what we've been previously been doing, or should we start adopting what FHS dictates here too and change things over to /opt/alpine/? 

 At present, installing into /opt is flagged by abuild as a policy violation.    The real question is whether /opt/$distribution should be exempted from the !fhs option.    That seems reasonable to me.  

However before accepting CouchDB into Alpine we should create a better policy for OTP releases.    For example, we do not wish to include the BEAM VM into the release, instead preferring the system package for it.

Ariadne