Re: [new] rrdp-tools (+ deps)

Stuart Henderson <[email protected]>
Newsgroups gmane.os.openbsd.ports
Message-ID <[email protected]>
On 2026/08/08 18:37, Theo Buehler wrote:
> On Sat, Aug 08, 2026 at 05:19:17PM +0100, Stuart Henderson wrote:
> > On 2026/08/08 14:58, Theo Buehler wrote:
> > > This is rrdp-tools command line utility suite which job wants to use.
> > > It's a bit painful to install with pip since as usual, this pulls in
> > > uv and ruff as most modern python tooling, and so you need to fiddle
> > > with --system-site-packages.
> > > 
> > > Unfortunately, the rrdp-tools don't currently have a license, so we
> > > need to set PERMIT_PACKAGE= No. Hopefully that will be fixed soon:
> > > https://github.com/ties/rpki-rrdp-tools-py/issues/55
> > > 
> > > All the dependencies can be packaged and distributed, so the tools can
> > > be installed with env FETCH_PACKAGES= make install, which is less hassle.
> > 
> > I would go with rrdp-tools-0.0.20260401 for the version, to reduce the
> > chance of needing EPOCH if they start making releases. (Or do something
> > based on the 0.4.0 version number in the filenames).
> 
> given that pyproject.toml has version 0.4.0 and 0.3.0, 0.2.1, 0.2.0
> existed over the past year, I think it makes sense to set
> 
> MODPY_DISTV=	0.4.0
> DISTNAME=	rrdp-tools-${MODPY_DISTV}pre0

Fine with me.

> + regen plist. This way we can bump to 0.4.0 if that is tagged/released
> or update to 0.5.0 if that should happen.
> 
> > 
> > > We need a bunch of dependencies (and deps thereof):
> > > 
> > > textproc/py-rnc2rng
> > 
> > could use MODPY_DISTV= ${GH_TAGNAME} + plist regen, dossn't really
> > matter though
> 
> done
> 
> > >   devel/py-rply
> > > security/py-asn1tools
> > >   devel/py-bitstruct
> > > sysutils/py-diskcache
> > > devel/py-alive-progress
> > 
> > stray /usr/local/LICENSE file, I'd @comment
> 
> done.
> 
> > >   textproc/py-graphemeu
> > >   sysutils/py-about-time
> > 
> > otherwise ok
> 
> thanks.
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.