Feel free to add it to the patch!

> Now 'emacs' directory contains a single git-controlled file -
> "guix-emacs.el".  It is used to patch our 'emacs' package (to find emacs
> packages in "share/emacs/site-lisp/guix.d").  But it is misplaced.

I agree.  May you can commit this patch first while we look for a
solution?

> What about making "gnu/packages/files" (or another dirname) directory,
> and putting "guix-emacs.el" and kernel configs ("linux-libre-*.conf")
> there?
>
> I mean "gnu/packages/patches" is not always enough, sometimes we want to
> use real files in the package recipes (configs for 'linux-libre' or
> "guix-emacs.el" for 'emacs'), so having "gnu/packages/files" seems
> reasonable to me, WDYT?

Sounds good.

In general, we can create other subdirectories alongside patches/ and
bootstrap/.  So we could have linux-conf/ and emacs/ there.  We can also
add regular files like guix-emacs.el directly under gnu/packages (like
ld-wrapper.in, linux-conf.*, etc.)

All this is fine as long as the files get installed in the right place
wrt. %load-path.

I’m not sure a catch-all files/ (or aux-files/?) directory is helpful
though.  There’s a case for having a linux-conf/ subdirectory now; for
guix-emacs.el, I am slightly inclined to put it directly in
gnu/packages, but no strong opinion.

Thoughts?

Thank you!

Ludo’.