# Re: \[PATCH v2 1/2\] perf tools: Put Python egg info in output directory

- From: Arnaldo Carvalho de Melo \<acme@kernel.org\>
- Date: 2026-09-28 16:27:01 
- List: linux-trace-kernel
- Page: https://ratatoskr.run/linux-trace-kernel/2026/09/17654571
- Thread: https://ratatoskr.run/linux-perf-users/2026/05/17015404/t.md

```text
On Mon, Sep 28, 2026 at 09:12:32AM -0700, Ian Rogers wrote:
> On Mon, Sep 21, 2026 at 10:57 AM Ian Rogers [ref] wrote:
> >
> > From: Ben Hutchings <redacted>
> >
> > Installing the Python extension currently creates an egg-info
> > directory in the source tree, preventing a fully out-of-tree build.
> >
> > Add the necessary runes to the setup.py comamnd line to relocate the
> > egg-info directory in an out-of-tree build.
> >
> > Signed-off-by: Ben Hutchings <redacted>
> > Reviewed-by: Ian Rogers <irogers@google.com>
> > ---
> > v2: Rebase
> 
> Ben's build clean up that I've then rebased and addressed an issue
> with building in tools/perf seems like a nice to land thing. I'm not
> sure what more I can do to push this forward, and I replied on the
> list about the Sashiko feedback, which was a little wide of the mark.
> Let me know what you think; perhaps the tags are not done properly.

I guess they are, you carried it forward and then pushed upstream, so
merits your Signed-off-by, I think.

Thanks, applied to perf-tools-next, for v7.4.

- Arnaldo
```
