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

Some rewording a tweaks.

Browse Source
This commit is contained in:
ajacoutot 2010-12-20 14:43:42 +00:00
parent 0ee0c3fc8e
commit 391b9471d9
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
print/cups/Makefile
View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.89 2010/12/20 11:39:48 ajacoutot Exp $ # $OpenBSD: Makefile,v 1.90 2010/12/20 14:43:42 ajacoutot Exp $
COMMENT= Common Unix Printing System COMMENT= Common Unix Printing System
@ -6,7 +6,7 @@ VERSION= 1.4.5
DISTNAME= cups-${VERSION}-source DISTNAME= cups-${VERSION}-source
PKGNAME= cups-${VERSION} PKGNAME= cups-${VERSION}
REVISION= 1 REVISION= 2
# Allow both ulpt(4) and libusb based backends to work together. # Allow both ulpt(4) and libusb based backends to work together.
# See http://www.cups.org/str.php?L3357 # See http://www.cups.org/str.php?L3357

6
print/cups/pkg/README
View File

@ -1,4 +1,4 @@
$OpenBSD: README,v 1.1 2010/12/20 11:39:48 ajacoutot Exp $ $OpenBSD: README,v 1.2 2010/12/20 14:43:42 ajacoutot Exp $
Using CUPS under OpenBSD Using CUPS under OpenBSD
======================== ========================
@ -14,7 +14,9 @@ package like (non-exhaustive list): hplip, gutenprint, foo2zjs, splix...
This package supports both ulpt(4) and libusb for printing to USB This package supports both ulpt(4) and libusb for printing to USB
devices. ulpt(4) should work out of the box, however: devices. ulpt(4) should work out of the box, however:
* it needs to claim the entire USB port, so it will not be possible to * it needs to claim the entire USB port, so it will not be possible to
access the scanner part of multi-function devices access the scanner part of a multi-function device
* ulpt(4) does not support select() which is used by CUPS to know when
the device can accept more data (http://www.cups.org/str.php?L3028)
* it won't be able to automatically detect the corresponding driver/PPD * it won't be able to automatically detect the corresponding driver/PPD
* it is deprecated upstream in favor of libusb * it is deprecated upstream in favor of libusb