From: Denis Shcherbakov <deniss@Princeton.EDU>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] SAMBA and CUPS conflict with LPRng
Date: Tue, 31 Dec 2002 00:18:50 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.44.0212310011180.21757-100000@yuma.Princeton.EDU> (raw)
Hello, folks,
I just wanted to ask what the deal is with the conflict between samba and
cups with lprng. I migrated from cups to lprng because it seems to work
much better for my systems for things like postscript printing and gnuplot
features. But I need samba too. However, with lprng on the system, samba
doesn't work because apparently it needs some cups libraries!
Samba doesn't REALLY need cups libs, does it? Only for certain
functionality, right? Is it possible to build samba without support for
printing? Like, edit the ebuild somehow? I don't need printing over
samba, but I do need to have it on my system and I do need lprng.
I'd appreciate any help as to how to resolve this.
Happy New Year! :)
Denis
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2002-12-31 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 5:18 Denis Shcherbakov [this message]
2002-12-31 5:23 ` [gentoo-dev] SAMBA and CUPS conflict with LPRng Greg Oliver
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=Pine.GSO.4.44.0212310011180.21757-100000@yuma.Princeton.EDU \
--to=deniss@princeton.edu \
--cc=gentoo-dev@gentoo.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