cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rework README after the recen ugen(4) default permissions change.

Browse Source 
Also sync the READMEs as close as possible.
This commit is contained in:
ajacoutot 2019-12-14 13:02:28 +00:00
parent 113a0946e1
commit d2e8650e22
6 changed files with 24 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
graphics/libgphoto2/Makefile
View File

@ -1,10 +1,11 @@
# $OpenBSD: Makefile,v 1.66 2019/06/15 09:14:19 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.67 2019/12/14 13:02:28 ajacoutot Exp $
COMMENT= digital camera library
VERSION= 2.5.23
DISTNAME= libgphoto2-${VERSION}
PKGNAME= libgphoto-${VERSION}
REVISION= 0
GPHOTO2_PORT_API= 0.12.0
SUBST_VARS= GPHOTO2_PORT_API VERSION

10
graphics/libgphoto2/pkg/README
View File

@ -1,11 +1,11 @@
$OpenBSD: README,v 1.1 2018/11/18 16:02:07 ajacoutot Exp $
$OpenBSD: README,v 1.2 2019/12/14 13:02:29 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${PKGSTEM} on OpenBSD
+-----------------------------------------------------------------------
Since USB reading of your camera will be handled by libusb, you need to
allow the user access to the corresponding USB endpoint. To do so, find
Since USB reading of your camera will be handled by libusb, you need to allow
the user access to the corresponding USB endpoint. To do so, find
where your camera is attached to by using:
$ usbdevs -v
then change the ownership accordingly.
@ -20,9 +20,5 @@ addr 03: 04e8:6860 SAMSUNG, SAMSUNG_Android
# chown <username> /dev/ugen0.* /dev/usb0
The reason we are changing the user and not the group is that only
<username> can access it.
To preserve your changes after a system update, use rc.local(8).
Alternatively, hotplugd(8) attach/detach scripts can automate this.

3
graphics/sane-backends/Makefile
View File

@ -1,10 +1,11 @@
# $OpenBSD: Makefile,v 1.86 2019/08/03 12:56:09 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.87 2019/12/14 13:02:28 ajacoutot Exp $
BROKEN-alpha= ICE hp5590.c:1141: error: unrecognizable insn
COMMENT= API for accessing scanners, backends
DISTNAME= sane-backends-1.0.28
REVISION= 0
SHARED_LIBS += sane 2.1 # unknown

20
graphics/sane-backends/pkg/README
View File

@ -1,4 +1,4 @@
$OpenBSD: README,v 1.16 2018/11/18 15:52:18 ajacoutot Exp $
$OpenBSD: README,v 1.17 2019/12/14 13:02:28 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${PKGSTEM} on OpenBSD
@ -8,8 +8,8 @@ First read ${TRUEPREFIX}/share/doc/sane-backends/PROBLEMS.
USB
===
Since USB scanning will be handled by libusb, you need to allow the
_saned user access to the corresponding USB endpoint. To do so, find
Since USB scanning will be handled by libusb, you need to allow
the user access to the corresponding USB endpoint. To do so, find
where your scanner is attached to using:
$ usbdevs -v
then change the ownerships accordingly.
@ -22,20 +22,14 @@ addr 05: 03f0:4812 HP, Officejet 7500 E910
driver: umass0
driver: ugen1
# chgrp _saned /dev/ugen1.* /dev/usb0
The reason we are changing the group and not the user is that it will
allow for multi-function devices to work for both printing and scanning
(e.g. by being owned by _cups:_saned).
# chown <username> /dev/ugen1.* /dev/usb0
To preserve your changes after a system update, use rc.local(8).
e.g. for a multi-function printer/scanner add the following lines:
chown _cups:_saned /dev/ugen1.* /dev/usb0
Alternatively, hotplugd(8) attach/detach scripts can automate this.
You can then grant users direct access to the scanner by adding them to
the _saned group.
You can grant multiple users direct access to the scanner by adding them to the
_saned group and allowing access to its ugen(4) device.
e.g. chgrp _saned /dev/ugen1.* && chmod 660 /dev/ugen1.*
SCSI
====

4
print/cups/Makefile
View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.252 2019/12/13 22:30:45 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.253 2019/12/14 13:02:28 ajacoutot Exp $
COMMENT-main= Common Unix Printing System
COMMENT-libs= CUPS libraries and headers
@ -11,6 +11,8 @@ GH_TAGNAME= v${VERSION}
PKGNAME-main= cups-${VERSION}
PKGNAME-libs= cups-libs-${VERSION}
REVISION-main= 0
CATEGORIES= print sysutils
# config-scripts/cups-sharedlibs.m4

17
print/cups/pkg/README-main
View File

@ -1,4 +1,4 @@
$OpenBSD: README-main,v 1.23 2019/09/29 13:25:15 ajacoutot Exp $
$OpenBSD: README-main,v 1.24 2019/12/14 13:02:28 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${PKGSTEM} on OpenBSD
@ -38,8 +38,8 @@ using it with CUPS on OpenBSD could work.
USB
===
Since USB printing will be handled by libusb, you need to allow the
_cups user access to the corresponding USB endpoint. To do so, find
Since USB printing will be handled by libusb, you need to allow
the _cups user access to the corresponding USB endpoint. To do so, find
where your printer is attached to using:
$ usbdevs -v
then change the ownerships accordingly.
@ -54,16 +54,13 @@ addr 05: 03f0:4812 HP, Officejet 7500 E910
# chown _cups /dev/ugen1.* /dev/usb0
The reason we are changing the user and not the group is that it will
allow for multi-function devices to work for both printing and scanning
(e.g. by being owned by _cups:_saned).
To preserve your changes after a system update, use rc.local(8).
e.g. for a multi-function printer/scanner add the following lines:
chown _cups:_saned /dev/ugen1.* /dev/usb0
Alternatively, hotplugd(8) attach/detach scripts can automate this.
For a multi-function devices to work for both printing and scanning, the ugen(4)
device must be accessed by both the _cups user and the _saned group:
e.g. chown _cups:_saned /dev/ugen1.* /dev/usb0 && chmod 660 /dev/ugen1.*
*** WARNING ***
ulpt(4) needs to be disabled in the kernel (see config(8)) or the printer
will not be available to libusb.