On 06/13/2016 06:45 AM, Jarod Wilson wrote:
On Fri, Jun 10, 2016 at 09:15:52PM -0400, Josh Boyer wrote:
> On Fri, Jun 10, 2016 at 5:25 PM, Jarod Wilson <jarod(a)redhat.com> wrote:
>> On Fri, Jun 10, 2016 at 12:42:59PM -0700, Miguel Flores Silverio wrote:
>>> Signed-off-by: Miguel Flores Silverio <floresmigu3l(a)gmail.com>
>>> ---
>>> scripts/fast-build.sh | 13 +++++++++++++
>>> 1 file changed, 13 insertions(+)
>>> create mode 100755 scripts/fast-build.sh
>>
>> You're busy eliminating pointless scripts, and then adding another one in
>> their place right here. :)
>
> Actually, this isn't pointless at all.
>
>> Just use the baseonly target in the spec, possibly with a patch to have
>> that also disable tools building to get exactly what you were after here.
>> Or add a target similar to baseonly for fastbuild.
>
> That could be done, but then people have to know all the various
> rpmbuild switches. It's a pain. From a novice user experience, it's
> very difficult to figure out. You have to know that target exists,
> which means reading the spec, which means understanding the spec,
> which is easy for you and I but is impossible as a _starting_ point.
>
> The purpose of the script is to give someone that just wants to build
> a kernel without all the crap a very easy thing to run. The intended
> user isn't us. It's so that we don't have to explain how to do it
> over and over (or point people to a confusing wiki page) to people
> that don't live in the kernel spec.
Fair enough, though are people really needing to build custom kernels that
often? (It's quite likely I'm out of touch with reality). :)
It happens more often than you think. A pretty common case is for a test
patch. Usually I end up giving a scratch build to have a bug reporter
verify that a patch works. It's less work for me (and possibly faster)
to have a reporter just make a build themselves.
Thanks,
Laura