mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: can support for "rpm"-based package building just be dropped?
Date: Mon, 26 Nov 2007 06:58:23 -0800	[thread overview]
Message-ID: <2c0942db0711260658j5ce017e7ucce4c373748ed7b7@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711260352060.30676@localhost.localdomain>

On Nov 26, 2007 12:54 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>   on current systems, "rpm" no longer has build capability and will
> fail thusly:
>
> rpm --target i386 -ta ../kernel-2.6.24rc3g2ffbb837dirty.tar.gz
> --target: unknown option
>
>   so it would make more sense to just require "rpmbuild" on the
> machine, would it not?

Only on current machines. You'd break building kernel RPMs on older
systems that don't have rpmbuild installed. So the change wouldn't fix
anything, and would break some non-zero number of setups that are
currently working, making the change a guaranteed net loss.

A patch that added version checks against rpm and whinged
appropriately about needing rpmbuild would likely be accepted, though.

  reply	other threads:[~2007-11-26 14:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26  8:54 Robert P. J. Day
2007-11-26 14:58 ` Ray Lee [this message]
2007-11-26 15:08   ` Robert P. J. Day
2007-11-26 15:12     ` Robert P. J. Day
2007-11-26 15:19       ` Ray Lee
2007-11-26 15:23   ` Jan Engelhardt
2007-11-26 15:53     ` Robert P. J. Day
2007-11-26 16:05       ` Jan Engelhardt
2007-11-26 16:13         ` Robert P. J. Day
2007-11-26 16:17           ` Jan Engelhardt
2007-11-27 13:37             ` Robert P. J. Day
2007-11-27 13:46             ` Olivier Galibert

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=2c0942db0711260658j5ce017e7ucce4c373748ed7b7@mail.gmail.com \
    --to=ray-lk@madrabbit.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    /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®