mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, USB list <linux-usb@vger.kernel.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: usbutils 0.81 release
Date: Mon, 27 Apr 2009 23:07:04 +0200	[thread overview]
Message-ID: <ac3eb2510904271407l7a480744s36d60025948aebd8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0904271645380.15670-100000@netrider.rowland.org>

On Mon, Apr 27, 2009 at 22:48, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Mon, 27 Apr 2009, Greg KH wrote:
>
>> Kay Sievers (11):
>>       rename configure.in -> configure.ac
>>       delete spec file
>
> Why delete the spec file?  Don't you want to keep it for people who
> would like to build an RPM?

Spec files are much too distro specific, they all contain custom
distro variables, reference package names which are not the same
across distros. They usually don't even agree on the directories the
stuff is installed into. The usb.ids file as an example, is in a
different location on every distro i have seen. :)

There is in most cases no point in keeping outdated spec files or
debian directories in upstream source packages. The best when updating
a package, is to start with the one that is in the source rpm of the
distro one uses.

Thanks,
Kay

  parent reply	other threads:[~2009-04-27 21:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 19:35 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
2009-04-29 20:23             ` Alan Stern
2009-04-27 21:07   ` Kay Sievers [this message]
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=ac3eb2510904271407l7a480744s36d60025948aebd8@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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

all inboxes | Powered by JetHome®