From: Max Kalika <max+lists.gentoo-dev@lsit.ucsb.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] cups x86 USE flag.
Date: Mon, 27 Jan 2003 15:53:37 -0800 [thread overview]
Message-ID: <77490000.1043711617@valkyrie.lsit.ucsb.edu> (raw)
Greetings Gentoo devs.
I have a question as to why the new cups ebuild tests for x86 to determine
whether or not to depend on hotplug (and consequently usbutils and
pciutiles). This flag is also not defined in IUSE.
The reason I bring this up is that on one machine I use cups as a print
server for a parallel printer and on another to connect to a network
enabled printer. I don't need hotplug support for cups in either case, but
I can't really disable those dependencies because the x86 USE flag is a
rather useful thing to have turned on. :-)
Wouldn't this functionality be better achieved with a "usb" or "hotplug"
USE flag? I realize that no such flag exists yet, but I can see it being
useful elsewhere so why not create it?
---max kalika
--max@lsit.ucsb.edu
-lsit systems administrator
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-01-27 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 23:53 Max Kalika [this message]
2003-01-28 2:13 ` [gentoo-dev] cups x86 USE flag Mike Frysinger
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=77490000.1043711617@valkyrie.lsit.ucsb.edu \
--to=max+lists.gentoo-dev@lsit.ucsb.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