From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Niels Basjes <Niels@Basjes.nl>, git@vger.kernel.org
Subject: Re: [PATCH] Two RPM building improvements
Date: Fri, 27 Mar 2009 15:45:21 +0100 [thread overview]
Message-ID: <49CCE681.5050503@drmicha.warpmail.net> (raw)
In-Reply-To: <m3k56b2hy2.fsf@localhost.localdomain>
Jakub Narebski venit, vidit, dixit 27.03.2009 14:50:
> Niels Basjes <Niels@Basjes.nl> writes:
>
>> Two RPM building improvements:
>
> Two _unrelated_ RPM building improvements squashed in one commit.
>
>> - Building the RPMs can now be done by a non-root user.
>
> It was always possible, you only have to configure rpm / rpmbuild,
> namely put path to where you want your RPM_BUILDING directory in
> ~/.rpmmacros as %_topdir, for example:
>
> $ cat ~/.rpmmacros
> %_topdir /home/local/builddir
>
> Please RTFM first, before going to solve non-problem in (ugh) fairly
> complicated way.
Also, the "solution" from the patch overrides any user choice from
.rpmmacros, AFAICS.
>
>> - The additional target all-rpms now builds the RPMs for a multitude of target platforms.
>
> Please wrap commit messages at 72-76 columns, at most at 80 columns.
> No such overly long lines, please.
>
> But the all-rpms target looks like a good idea
>
next prev parent reply other threads:[~2009-03-27 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 12:32 [PATCH] Two RPM building improvements Niels Basjes
2009-03-27 13:50 ` Jakub Narebski
2009-03-27 14:45 ` Michael J Gruber [this message]
2009-03-27 16:20 ` Junio C Hamano
2009-03-27 19:43 ` Michael J Gruber
-- strict thread matches above, loose matches on Subject: below --
2009-03-27 16:07 Niels Basjes
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=49CCE681.5050503@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Niels@Basjes.nl \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.