Bug 221776 - [NEW PORT] dns/unbound-python: Slave port with python option enabled
Summary: [NEW PORT] dns/unbound-python: Slave port with python option enabled
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Yuri Victorovich
URL:
Keywords:
Depends on:
Blocks: 221636
  Show dependency treegraph
 
Reported: 2017-08-24 20:01 UTC by Vidar Karlsen
Modified: 2018-05-08 18:38 UTC (History)
2 users (show)

See Also:


Attachments
shar file for dns/unbound-python (815 bytes, text/plain)
2017-08-24 20:01 UTC, Vidar Karlsen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vidar Karlsen 2017-08-24 20:01:55 UTC
Created attachment 185727 [details]
shar file for dns/unbound-python

dns/unbound is built without python support by default.

This slave port adds python support, to allow python modules for Unbound to be ported and packaged.
Comment 1 Yuri Victorovich freebsd_committer 2017-08-26 19:18:30 UTC
I don't think it is the right solution to have a slave port for just the python option difference.

The problem: in case some users will want it with PYTHON=on and some - with PYTHON=off, this will cause conflicts.

The right solution: to split out the python binding from dns/unbound into a separate port, dns/py-unbound. This way dependent ports can use any involved packages without conflicts.

Please correct this, and create a dns/py-unbound instead.


Regards,
Yuri
Comment 2 w.schwarzenfeld freebsd_triage 2018-05-08 18:38:57 UTC
dns/unbound has configure options:

/usr/ports/dns/unbound/work/unbound-1.7.0/configure --help:

 --with-pyunbound        build PyUnbound, or --without-pyunbound to skip it.
                          (default=no)
  --with-pythonmodule     build Python module, or --without-pythonmodule to
                          disable script engine. (default=no)