Junio C Hamano venit, vidit, dixit 27.03.2009 17:20: > Jakub Narebski <jnareb@xxxxxxxxx> writes: > >> Niels Basjes <Niels@xxxxxxxxx> 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. I assumed everyone building rpms would use rpmdev-setuptree from rpmdevtools, but apparently not ;) I'm not sure whether non-Redhat rpm-based distros have that, though. I'm wondering a bit about the all-rpms target. How does this work without mock? All build requirements installed for all platforms?? I think it really calls for a mock build/vm (unless i386 on x86_64). Michael -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
