https://github.com/qbit/openbsd-backports
Backports of various things from -current
https://github.com/qbit/openbsd-backports
Last synced: 3 months ago
JSON representation
Backports of various things from -current
- Host: GitHub
- URL: https://github.com/qbit/openbsd-backports
- Owner: qbit
- License: mit
- Created: 2017-07-30T15:21:55.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2017-07-30T19:29:36.000Z (almost 9 years ago)
- Last Synced: 2025-01-16T13:46:49.982Z (over 1 year ago)
- Language: Makefile
- Size: 3.91 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
openbsd-backports
==================================
Tree of OpenBSD ports that have been 'back ported' to work with the current stable
release of OpenBSD.
The main goal is to bridge the gap between ports and versions of ports that only
exist in the -current ports tree.
*OpenBSD OFFERS NO SUPPORT FOR THIS TREE, USE AT YOUR OWN RISK!*
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-backports:${PORTSDIR}/mystuff
In the above example, a port with version 1 in cvs, version 2 in openbsd-backports.
Then, the version in cvs will be picked up before the version in openbsd-backports.
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-backports repo
(see git-config(1) on `branch..rebase` and `branch.autosetuprebase`):
git config branch.master.rebase true
Users of `py-hg-git` may update the tree issuing:
hg pull --rebase
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