From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Ray Lee <ray-lk@madrabbit.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: can support for "rpm"-based package building just be dropped?
Date: Tue, 27 Nov 2007 08:37:37 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0711270835380.21411@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0711261716220.22369@fbirervta.pbzchgretzou.qr>
On Mon, 26 Nov 2007, Jan Engelhardt wrote:
>
> On Nov 26 2007 11:13, Robert P. J. Day wrote:
> >> >>>Only on current machines. You'd break building kernel RPMs on older
> >> >>>systems that don't have rpmbuild installed.
> >> >>
> >> >> Those old machines probably do not even run a distro-fabricated
> >> >> gcc that would compile a git head kernel.
> >> >
> >> >well, in a nutshell, the problem scenario is that it's entirely
> >> >possible to have a modern distro (say, fedora 8, like i'm using) on
> >> >which you have the latest "rpm" package installed, but not
> >> >"rpmbuild".
> >>
> >> What, modern and no rpmbuild?
> >
> >i didn't say it *wouldn't* have rpmbuild, i said it *might not*.
> >at the moment, on my f8 system, the only package that requires the
> >rpm-build package is rpmdevtools, and it's entirely possible that
> >there's no need for *that* package.
>
> rpm -b does not work in opensuse anymore (redirects you to use
> rpmbuild), and I bet fedora will do the same, so if you don't have
> rpm-build, tough luck for make rpm.
i know that that's the case *now*, but we're considering the
possibility that someone is using an older system on which "rpm" is
*still* the builder. in the end, all i'm suggesting is that the build
should work under all possible scenarios.
rday
p.s. i'm not *trying* to make this issue more obfuscated or
convoluted than it has to be -- i am merely succeeding.
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-11-27 13:39 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
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 [this message]
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.0711270835380.21411@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=jengelh@computergmbh.de \
--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®