py-pyangValidator and code generator for YANG (RFC 4741)
2.4.0net-mgmtΣ=0 2.1.1Version of this port present on the latest quarterly branch.upstream: 2.5.0A newer version was found upstream by portscout, first on 2026-11-16.
YANG is a data modeling language for NETCONF (RFC4741), developed
by the IETF NETMOD WG.
pyang is a YANG validator, transformator and code generator, written
in python. It can be used to validate YANG modules for correctness,
to transform YANG modules into other formats, and to generate code
from the modules.
pyang is compatible with
http://www.ietf.org/internet-drafts/draft-ietf-netmod-yang-02.txt.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py312-pyang listed in the above command, you can pick from the names under the Packages section.
*/*: switch dependency from devel/py-lxml5 to devel/py-lxml
Currently, there are two versions of python XML processing library
which conflict each other in the ports tree, namely:
- devel/py-lxml5 (now at version 5.4.0)
- devel/py-lxml (now at version 6.0.1)
To avoid the situation that some ports depend on py-lxml5 and some
others do on py-lxml (by switching dependencies individually), this
commit switches the dependencies from py-lxml5 to py-lxml at once.
Additional note: There are still two ports (textproc/py-rdflib and
www/py-draftjs-exporter) depending on py-lxml5 since they limit upper
version to less than 6.
PR: 289491
Approved by: Michiel van Baak Jansen <michiel@vanbaak.eu>, arrowd,
crees, madpilot, delphij, marcus, nivit, kai,
skreuzer, fluffy, bofh, thierry, stephen, sunpoet,
0mp, Eric Camachat <eric@camachat.org>
*/*: update dependency on devel/py-lxml to devel/py-lxml5 (2nd attempt)
This is a follow up to the commit 230fb2661c78, which updated some
ports' dependencies on devel/py-lxml to devel/py-lxml5. It was an
attempt to follow the dependency change of
www/py-beautifulsoup. However, the switch was incomplete and broke
some other ports.
It has turned out that the ports depending on devel/py-lxml (at
version 4.9.3) does not limit their dependencies' upper bound to 4.x
except for one (devel/py-pymaven-patch). So updating them to
devel/py-lxml5 (at version 5.4.0) should cause no harm.
This commit switch dependencies of all the ports (except
devel/py-pymaven-patch) to devel/py-lxml5 avoid potential conflicts.
Co-authored-by: Daniel Engberg <diizzy@FreeBSD.org>
PR: 287144, 288047
Reported by: makc (via ports-committers),
vvd (PR 288047),
diizzy (PR 287144)
Approved by: portmgr (chase dependency change, unbreak build)
Fixes: 230fb2661c78 (*/*: update dependency on devel/py-lxml to devel/py-lxml5)
python: bump all USE_PYTHON=distutils consumers after RUN_DEPENDS removal
Any missed ports, feel free to bump.
Any ports that need setuptools at runtime can have the devel/py-setuptools
manually added back to RUN_DEPENDS, but understand that this practice
is deprecated; see CHANGES for details.
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
net-mgmt/py-pyang: Unbreak and Update version 1.4.1=>1.7.1
- Change MASTER_SITES to CHEESESHOP from GOOGLECODE
- Mark NO_ARCH
- Use autoplist for python
Submitted by: borge.brunes@uit.no
GOOGLE_CODE has gone away.
- If a port has another upstream, remove GOOGLE_CODE
- If a port only has GOOGLE_CODE mark it BROKEN
Some ports have a local mirror configured but for security reasons, it
is not considered upstream.
Sponsored by: Absolight
- update to 1.1
- trim Makefile header
- add license (BSD)
- limit python version to 2.x
- add patch to not install LICENSE once again and to fix MANPREFIX1
- remove reinplace that is now handled with aforementioned patch
- install yang2dsdl, yang2html and update TODO
Drop maintainership for these ports.
Regrettably, I have no free time for the foreseeable future which
I can commit directly to these aspects of FreeBSD work, due to
a demanding new role elsewhere.
I am able to review patches from time to time, but regrettably cannot
be directly involved in engineering work beyond this w/o it being
directly involved in day-to-day effort.
Thank you for your understanding.