mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Ray Lee <ray-lk@madrabbit.org>
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 10:12:37 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0711261010480.22378@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711261007370.22202@localhost.localdomain>

On Mon, 26 Nov 2007, Robert P. J. Day wrote:

> On Mon, 26 Nov 2007, Ray Lee wrote:
>
> > 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.
>
> yes, i suspect that's the right answer.
>
> rday

BTW, is there someone who knows what the relevant version is of "rpm"
that stopped incorporating the packaging functionality?  i'm a bit
swamped today but if someone wants to whip up a patch and get it in
before the next major release, that would be useful, i would think.

in short, can someone else handle this?  :-)

rday

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

  reply	other threads:[~2007-11-26 15:14 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
2007-11-26 15:08   ` Robert P. J. Day
2007-11-26 15:12     ` Robert P. J. Day [this message]
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=alpine.LFD.0.9999.0711261010480.22378@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-lk@madrabbit.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

all inboxes | Powered by JetHome®