lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFynFze+AJxUtkiAaOTJ58cK8=aiDi-fQqQ3bDV54w-=+A@mail.gmail.com>
Date:	Wed, 28 Mar 2012 12:46:25 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arnaldo Carvalho de Melo <acme@...radead.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Jiri Olsa <jolsa@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] perf tools: Including pre-generated flex files

On Tue, Mar 27, 2012 at 11:15 AM, Arnaldo Carvalho de Melo
<acme@...radead.org> wrote:
>
>        But Ingo argues that flex and bison are just a yum/whatever
> install away, so we shouldn't clutter the kernel git history with things
> we can generate at build time.
>
>        What is your take on this?

I think I agree.

Building the *basic* kernel is different - I want people to be able to
build the kernel and install it and test it out with a fairly minimal
development environment.

But the perf tools
 (a) are mainly useful for developers who can easily install these
things *anyway* (ie we're not talking the same kind of usage cases
where we want to encourage random people off the street to build and
test)
 (b) already require things that are *much* less common than flex (ie
the whole libelf-devel stuff etc)
so I think having pre-generated lex/yacc files is just silly - just
install the tool.

                    Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ