Re: FHS 3.8: /opt/<package>/
> How does one resolve /opt conflicts between similar packages being released
> from separate sources? What does one do if there are two or more java,
> cc, etc?
Please don't use /opt. It makes your packages hard to use in a networked
environment.
That aside the same issue comes up with /usr/bin and the like too. I don't
think there is an easy answer to it. For many things its implicitly obvious
what people expect (eg if your default cc is not gcc you will never be able
to do any useful package building on Linux), java I don't know. Do we
actually want to become name space policemen ?
Reply to: