This comprises 3 subpackages, libisoburn, xorriso and xorriso-tcltk:
libisoburn is a frontend for libburn and libisofs libraries which
enables creation and expansion of ISO-9660 filesystems on all CD/DVD/BD
media supported by libburn. This includes media like DVD+RW, which do
not support multi-session management on media level and even plain disk
files or block devices.
xorriso copies file objects from POSIX compliant filesystems into Rock
Ridge enhanced ISO 9660 filesystems and allows session-wise manipulation
of such filesystems. It can load the management information of existing
ISO images and it writes the session results to optical media or to
filesystem objects.
xorriso-tcltk is a GUI frontend to xorriso.
Note that this (along libburn and libisofs) replaces/supersedes
sysutils/xorriso.
ok sthen@ uaa@
libburn is a library by which preformatted data get onto optical media:
CD, DVD, BD (Blu-Ray). On OpenBSD it uses /dev/cdNc.
libburn also offers a facility for reading data blocks from its drives
without using the normal block device i/o, which has its advantages and
disadvantages. It seems appropriate, nevertheless, to do writing and
reading via the same channel.
ok sthen@ uaa@
libisofs is a library to create an ISO-9660 filesystem with extensions
like Rock Ridge or Joliet. It is also a full featured ISO-9660 editor,
allowing you to modify an ISO image or multisession disc, including
file addition/removal, change of file names and attributes, etc.
ok sthen@ uaa@
Note that there is no xattr support on OpenBSD so we're not affected by
all the bugs upstreams fixed
discussed with jca, naddy and espie
ok espie (maintainer)
Note that this is a major upgrade from the 0.8 branch, see
http://docs.buildbot.net/current/manual/installation/nine-upgrade.html
for details on how to deal with it.
If you were running a 0.8 buildmaster and want to keep running it to
access old build logs, it's advised to install it locally outside of
ports/packages via pip.
The buildbot port is now split into 6 distinct sub-ports.
ok sthen@ (thanks!)
No bump needed since either the package doesn't change or it didn't
build before. Note that aarch64 is still broken (undefined references
to pthread_foo at link time). ok pirofti@ (maintainer)
Spin is a software verification tool for analyzing the consistency of
asynchronous systems. Examples of asynchronous systems include multi-threaded
programs, distributed systems, and communications protocols. Spin takes a
system model specified in Promela (the PROcess MEta LAnguage). It also takes
a specifciation of the requirements for logical correctness, and allows both
interactive and exhaustive simulations of the system for verifying these
properties.
Submission by Ori Bernstein <ori@eigenstate.org>
OK bcallah@
From Klemens Nanni, thanks!
toot lets you read, post and manage accounts on Mastadon social networks. It
supports logging in through both your webbrowser and the console with optional
two factor authentication. Toots can be pasted directly via standard input.
Autobahn|Python is a subproject of Autobahn and provides open-source
implementations of the WebSocket Protocol and the Web Application
Messaging Protocol (WAMP) for Python 2 and 3, and running on Twisted
and asyncio.
You can use Autobahn|Python to create clients and servers in Python
speaking just plain WebSocket or WAMP.
WebSocket allows bidirectional real-time messaging on the Web and
beyond, while WAMP adds real-time application communication on top of
WebSocket.
WAMP provides asynchronous Remote Procedure Calls and Publish &
Subscribe for applications in one protocol running over WebSocket.
WAMP is a routed protocol, so you need a WAMP Router to connect your
Autobahn|Python based clients. We provide Crossbar.io, but there are
other options as well.
needed by buildbot 0.9. A python3 flavor might be added later on..
ok sthen@
txaio is a helper library for writing code that runs unmodified on both
Twisted and asyncio / Trollius.
This is like six, but for wrapping over differences between Twisted and
asyncio so one can write code that runs unmodified on both (aka source
code compatibility). In other words: your users can choose if they want
asyncio or Twisted as a dependency.
Note that, with this approach, user code runs under the native event
loop of either Twisted or asyncio. This is different from attaching
either one’s event loop to the other using some event loop adapter.
needed by buildbot 0.9.
ok sthen@
