From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Benny Amorsen <benny+usenet@amorsen.dk>,
Alan Stern
<public-stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@hugh.gmane.org>,
Greg KH <public-greg-U8xfFu+wG4EAvxtiuMwx3w@hugh.gmane.org>,
Kay Sievers <public-kay.sievers-tD+1rO4QERM@hugh.gmane.org>,
USB list <public-linux-usb-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org>,
Kernel development list
<public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org>
Subject: Re: usbutils 0.81 release
Date: Wed, 29 Apr 2009 10:42:32 -0700 [thread overview]
Message-ID: <20090429174232.GA29026@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0904291150200.24643-100000@netrider.rowland.org>
On Wed, Apr 29, 2009 at 11:51:12AM -0400, Alan Stern wrote:
>
>
>
> On Wed, 29 Apr 2009, Benny Amorsen wrote:
>
> > Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>
> > writes:
> >
> > > Sure they do. If you've got an RPM-based system, and you want to
> > > install a package version that's more recent than the one bundled in
> > > your distribution (or if your distribution doesn't include the package
> > > at all), then you'd want to build your own RPM.
> >
> > In that case you grab the source package from the distribution, install
> > it, bump the version number and add the tar file to the SOURCES
> > directory. (And then you remove the patches which were upstreamed in the
> > meantime).
>
> You didn't read all that I wrote. What if the package isn't included
> in the distribution at all?
What rpm based distro does not have usbutils?
Just curious,
greg k-h
next prev parent reply other threads:[~2009-04-29 18:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 19:35 usbutils 0.81 release Greg KH
2009-04-27 20:48 ` Alan Stern
2009-04-27 21:00 ` Greg KH
2009-04-27 21:21 ` Alan Stern
2009-04-27 21:36 ` Kay Sievers
2009-04-29 14:23 ` Benny Amorsen
2009-04-29 15:51 ` Alan Stern
2009-04-29 17:27 ` Mike Frysinger
2009-04-29 17:42 ` Greg KH [this message]
2009-04-29 20:23 ` Alan Stern
2009-04-27 21:07 ` Kay Sievers
2009-04-27 21:54 ` Alan Stern
2009-04-27 22:02 ` Kay Sievers
2009-04-29 17:53 ` Mike Frysinger
2009-04-29 18:07 ` Greg KH
2009-04-29 18:17 ` Mike Frysinger
2009-04-29 18:30 ` Greg KH
2009-04-29 23:38 ` Mike Frysinger
2009-04-30 0:45 ` Kay Sievers
2009-04-30 1:48 ` Mike Frysinger
2009-04-30 1:54 ` Kay Sievers
2009-04-30 1:58 ` Mike Frysinger
2009-04-29 18:59 ` Kay Sievers
2009-04-29 19:18 ` Henrique de Moraes Holschuh
2009-04-29 19:26 ` Greg KH
2009-04-29 19:44 ` Kay Sievers
2009-04-29 19:27 ` Kay Sievers
2009-04-29 19:50 ` Henrique de Moraes Holschuh
2009-04-29 19:55 ` Kay Sievers
2009-04-29 20:00 ` Henrique de Moraes Holschuh
2009-04-29 20:39 ` Kay Sievers
2009-04-30 6:31 ` Bjørn Mork
2009-04-29 19:23 ` Greg KH
2009-04-29 21:42 ` Valdis.Kletnieks
2009-04-29 21:56 ` Greg KH
2009-04-29 22:19 ` Valdis.Kletnieks
2009-04-30 1:48 ` Kay Sievers
2009-04-30 1:56 ` Mike Frysinger
2009-04-30 2:06 ` Kay Sievers
2009-04-30 2:13 ` Mike Frysinger
2009-04-30 4:54 ` Greg KH
2009-04-29 21:57 ` Kay Sievers
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=20090429174232.GA29026@kroah.com \
--to=greg@kroah.com \
--cc=benny+usenet@amorsen.dk \
--cc=public-greg-U8xfFu+wG4EAvxtiuMwx3w@hugh.gmane.org \
--cc=public-kay.sievers-tD+1rO4QERM@hugh.gmane.org \
--cc=public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
--cc=public-linux-usb-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
--cc=public-stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@hugh.gmane.org \
--cc=stern@rowland.harvard.edu \
/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