From: "Tiziano Müller" <dev-zero@gentoo.org>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH] Use cups-config instead of hardcoded location
Date: Tue, 07 Apr 2009 10:59:59 +0200 [thread overview]
Message-ID: <1239094799.19235.2.camel@localhost> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 142 bytes --]
Hi there
This patch has been sitting in our cvs repo for ages:
Use cups-config instead of hardcoded cups-location.
Thanks,
Tiziano
[-- Attachment #1.2: cups-location.patch --]
[-- Type: text/x-patch, Size: 498 bytes --]
? cups/.deps
? cups/Makefile
? cups/Makefile.in
Index: cups/Makefile.am
===================================================================
RCS file: /cvsroot/bluez/utils/cups/Makefile.am,v
retrieving revision 1.9
diff -u -r1.9 Makefile.am
--- cups/Makefile.am 20 Aug 2006 02:21:03 -0000 1.9
+++ cups/Makefile.am 1 Jun 2007 15:47:14 -0000
@@ -1,6 +1,6 @@
if CUPS
-cupsdir = $(libdir)/cups/backend
+cupsdir = `cups-config --serverbin`/backend
cups_PROGRAMS = bluetooth
else
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-04-07 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 8:59 Tiziano Müller [this message]
2009-04-07 10:25 ` [PATCH] Use cups-config instead of hardcoded location Bastien Nocera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1239094799.19235.2.camel@localhost \
--to=dev-zero@gentoo.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox