From: Junio C Hamano <gitster@pobox.com>
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 09:20:47 -0700 [thread overview]
Message-ID: <7vvdpvdjj4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: m3k56b2hy2.fsf@localhost.localdomain
Jakub Narebski <jnareb@gmail.com> writes:
> 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.
That might be a bit too harsh to somebody who genuinely wished to share
his improvement with others.
Being RPM novice, the first thing I asked around immediately after taking
the maintainership over was the ~/.rpmmacros trick. We really should
mention it in _our_ documentation, even just a sentence or two would be
sufficient.
next prev parent reply other threads:[~2009-03-27 16:22 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
2009-03-27 16:20 ` Junio C Hamano [this message]
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=7vvdpvdjj4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).