[Slackbuilds-users] Additional REQUIRES entries
erich.public at protonmail.com
Fri Jan 31 15:02:33 UTC 2020
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, January 31, 2020 5:28 AM, Christoph Willing <chris.willing at linux.com> wrote:
> On 31/1/20 9:30 pm, B Watson wrote:
> > On 1/31/20, Christoph Willing chris.willing at linux.com wrote:
> > > [opencv]
> > > QK_REQUIRES = libdc1394 ffmpeg
> > > Of course, just add more entries as needed. Also, multiple quirks files
> > > can be maintained for special purposes, changing between them using the
> > > new -q option.
> > Is there a mechanism for keeping track of environment variables,
> > preferably in the same quirks file? As an example, ffmpeg has a ton
> > of optional FOO=yes BAR=yes and pretty much everyone wants/needs a
> > different set of them for their personal ffmpeg build. I have an "env"
> > file to source, in my local git tree (untracked, just sitting in the
> > ffmpeg dir) but it's not what you'd call an ideal solution.
> > Also you got stuff that has REQUIRES="python3", and the README says
> > python-something is optional (good candidate for quirks file), but
> > python-something has to be run with PYTHON3=yes in the env (doesn't
> > autodetect).
> Yes, I also store environment variables in the quirks file - it's what I
> was alluding to as "possible further use of a quirks file" in the
> original email but didn't elaborate on as it was already so long.
FYI slackrepo handles this using hintfiles (http://idlemoor.github.io/slackrepo/hintfiles.html).
This is my qt5.hint:
OPTIONS="DOCS=yes EXAMPLES=yes PROPRIETARY_CODECS=yes"
ADDREQUIRES="libwebp opus pcre2 snappy"
More information about the SlackBuilds-users