From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb
Date: Sat, 9 Nov 2013 17:57:23 -0600 [thread overview]
Message-ID: <20131109235723.GA29602@crud> (raw)
In-Reply-To: <20131109182553.e20f212f81585d215108f553@comcast.net>
Frank Peters <frank.peters@comcast.net> skribis:
> Fork? Who's gonna take on that challenge? It seems that a handful
> of developers, with their own special and exclusionary agenda, will control
> the Linux GE for all time.
Forking the bulk of this stuff isn’t very productive, because it’s not
good enough to improve upon significantly. At best what can be done by
forking is stuff like eudev, hacks to try to minimize the damage.
It’s just not competent software, as a whole. What am I to make of it,
that I have to use OpenBSD’s pkg-config clone, because the one from
freedesktop, the most basic piece of software in the system, does not
work correctly? I think they haven’t even done something as simple as
properly maintain the serial number of pkg.m4.
next prev parent reply other threads:[~2013-11-09 23:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 3:25 [gentoo-amd64] USB Scanner Problems with Newer Kernels/Libusb Frank Peters
2013-11-09 12:29 ` [gentoo-amd64] " Duncan
2013-11-09 16:45 ` Frank Peters
2013-11-09 20:40 ` Barry Schwartz
2013-11-09 21:38 ` Frank Peters
2013-11-09 22:11 ` Barry Schwartz
2013-11-09 22:57 ` Mark Knecht
2013-11-09 23:10 ` Barry Schwartz
2013-11-10 16:54 ` Tanstaafl
2013-11-10 17:08 ` Barry Schwartz
2013-11-09 23:25 ` Frank Peters
2013-11-09 23:57 ` Barry Schwartz [this message]
2013-11-10 1:30 ` [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb [Solved] Frank Peters
2013-11-10 1:53 ` Barry Schwartz
2013-11-10 2:36 ` Frank Peters
2013-11-10 4:26 ` Frank Peters
2013-11-12 0:03 ` Frank Peters
2013-11-12 23:18 ` [gentoo-amd64] " Jörg Schaible
2013-11-13 9:14 ` Paul Jewell
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=20131109235723.GA29602@crud \
--to=chemoelectric@chemoelectric.org \
--cc=gentoo-amd64@lists.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