• Stars
    star
    267
  • Rank 153,621 (Top 4 %)
  • Language
    C++
  • Created about 13 years ago
  • Updated 28 days ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

OpenBSD work in progress ports

openbsd-wip - work in progress ports for OpenBSD

This tree is to be used to maintain and eventually migrate ports into the official OpenBSD ports tree. This means that ports in this tree are actively worked on and may not always build, though of course it's best to aim for building ports.

The goal of this exercise is to get more people actively involved in ports. As well as having a tool to better keep track of (half-)finished ports out there. Instead of having it rot in a corner of a mailinglist.

Updated ports

Updates are also welcome; just try to keep this tree clean by removing ports that are updated/imported upstream.

If you're importing an update, please add an UPDATE file in the ports' directory with a summary of changes/explanation. This will make it easier to keep updates and new ports apart.

If it's a rather trivial update, please don't bother importing it here and just send the diff to ports@ and/or the maintainer.

Finished ports

When a port is ready to get committed, please add an entry to /FINISHED in the following format (subject to change):

net/gnaughty:	ready for import, sent to ports@ (jasperla)

Use a TODO file to list what the outstanding issues are before the port can be listed in FINISHED.

Also, only commit full ports please. Not just a Makefile or just a diff.

Administrative files

As one of the main goals of this repository is to ease the workload for committers, please use the following files to keep the overview of what's here:

  • FINISHED: Described above
  • TODO: File in the ports' directory explaining what needs to be done
  • UPDATE: Explain the update, could contain a ready-to-use commit message? :)
  • ABANDONED: Ports that have not seen any activity in recent years nor have any licensing restrictions that would prevent them from ever being imported into CVS.

Workflow (open for discussion)

  • Commit your updated port here with a corresponding UPDATE file.
  • or commit your new port WIP-update here with a TODO/UPDATE file and hack on it.
  • Mail ports@ and/or maintainer.
  • Add an entry to FINISHED.
  • When the port is committed, remove the FINISHED entry as well as the port.

This repository is not here to migrate people away from using ports@. Ports posted here are unlikely to get the level of discussion and testing they get on ports@. So this repository is here to keep track of the submissions.

If you don't want to work anymore on your half-finished or not-committed-yet port, please remove it from the repository. In the future, other people can rescue your work from the git history. Maintaining the repository will prevent it from becoming a graveyard of abandoned ports.

Branches

Ideally this repo should contain only one branch, where all development happens. If you want to create a feature branch, please consider avoiding it. Most likely your feature branch will desync from master, making it difficult to merge and, after some time, difficult to locate in the repo. Most likely you only need edit a handful of ports, so just directly editing them in master will work. If you really need a feature branch, please, merge it back as soon as you know whether things worked out or not.

How to use this tree

One way to use this tree is to clone it into your /usr/ports/ directory and adjust PORTSDIR_PATH accordingly in /etc/mk.conf:

PORTSDIR_PATH=${PORTSDIR}:${PORTSDIR}/openbsd-wip:${PORTSDIR}/mystuff

In the above example, a port with version 1 in cvs, version 2 in openbsd-wip. Then, the version in cvs will be picked up before the version in openbsd-wip. This is important if you are building packages using dpb. The order of PORTSDIR_PATH is important.

To prevent "merge commits" from showing up in git log, it's recommended to either update your tree with:

git fetch && git rebase origin

or set the following option in .git/config in your local openbsd-wip repo (see git-config(1) on branch.<name>.rebase and branch.autosetuprebase):

git config branch.master.rebase true

How to contribute

Please let me know if you need write access to this repository. But please stick the workflow outlined in this document as well the pointers in https://openbsd.org/porting.html

More Repositories

1

CVE-2020-11651-poc

PoC exploit of CVE-2020-11651 and CVE-2020-11652
Python
119
star
2

node-vcard

parse vCard files/data into JSON
JavaScript
55
star
3

openbsd-rockpro64

OpenBSD/arm64 on PINE64 RockPro64
31
star
4

portroach

OpenBSD ports tree version scanner
Perl
17
star
5

CVE-2017-9101

Exploit for PlaySMS 1.4 authenticated RCE
Python
14
star
6

tinyschemg

mg(1) extended with tinyscheme
C
9
star
7

ansible-vmm

Playground for Ansible modules for vmm(4)
Python
8
star
8

hwsensorsbeat

Lightweight shipper for OpenBSD sensors information
Go
7
star
9

clj-mpd

Moved to clj-mpd/clj-mpd
Clojure
5
star
10

realtek_turnkey_decrypter

C
4
star
11

node-pdflatex-ng

pdflatex(1) wrapper for Node.js
JavaScript
4
star
12

munin-mpower

Munin plugin for mPower devices
Ruby
3
star
13

puppet-mfi

Ubiquiti mFi module for Puppet
Puppet
2
star
14

openbsd_facts

Various OpenBSD facts for facter
Ruby
2
star
15

gmc4-as

Simple assembler for GMC4
Perl
2
star
16

prism-langs

prism.js language components
JavaScript
2
star
17

ansible-dsapid

Ansible playbook for dsapid
Python
2
star
18

salt-tls-formula

SaltStack
1
star
19

gitbot

Jabber bot for github interaction
Clojure
1
star
20

btrace-fuzz

1
star
21

jasperla.github.com

HTML
1
star
22

gmc4-snippets

Random pieces of code for the GMC4
Assembly
1
star
23

netbox-zone-generator

DNS zone generation based on netbox prefixes
Python
1
star
24

favicommh3

HTML
1
star
25

icb-rs

Simple ICB library and client written in Rust
Rust
1
star
26

dot.files

Lua
1
star
27

oh-my-zsh

trimmed fork of oh-my-zsh
Shell
1
star
28

puppet-procmail

Puppet module to manage procmail and generate a procmailrc
Puppet
1
star
29

dot.emacs

Random collection of snippets that make up my .emacs.d
Emacs Lisp
1
star
30

sonosq

Copy Sonos queues between speakers
Ruby
1
star
31

docker-tags

Track and report tags of followed Docker images
Ruby
1
star
32

sonvol

Simple Sonos volume control. Nothing fancy, just volume control.
Ruby
1
star
33

tadpole

URI collecting IRC bot
CoffeeScript
1
star