unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brett Gilio <brettg@posteo.net>
To: 38613@debbugs.gnu.org
Subject: bug#38613: Disabling bytecompilation on a list of files.
Date: Sat, 14 Dec 2019 13:45:10 -0600	[thread overview]
Message-ID: <87tv62itdl.fsf@posteo.net> (raw)

Hey all.

Just forwarding along an idea discussed between Leo Prikler, Tobias, and
I on IRC.

Recently I was trying to update our emacs-doom-themes package to a
fresher commit since it offers numerous new functionalities but there is
not a marked stable release of the package. In the process I found an
issue where some files have a bytecode compilation overflow issue during
the build phase. My sloppy work around as shown in
e9d8dee6c3d6e2ddff74841a3ab3a2ba2816bf27 was as such:

--8<---------------cut here---------------start------------->8---
;; XXX: There is a byte-code overflow issue in the latest
;; checkout which affects byte-compilation for several theme
;; files. The easiest way to work around this is to disable
;; byte-compilation until the issue is resolved.
;; <https://github.com/hlissner/emacs-doom-themes/issues/314>
(delete 'build)
--8<---------------cut here---------------end--------------->8---

Obviously just outright deleting the phase responsible for
bytecompilation is not the _best_ solution. So what Leo and I proposed
was adding a #:no-bytecomp which takes a list of REGEXP or files that
will be excluded from the in-place byte-compilation.

I wanted to float this idea by those of us who use the
emacs-build-system regularly.

Thanks!

-- 
Brett M. Gilio
Homepage -- https://scm.pw/
GNU Guix -- https://guix.gnu.org/

             reply	other threads:[~2019-12-14 23:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14 19:45 Brett Gilio [this message]
2019-12-15  0:35 ` bug#38613: Disabling bytecompilation on a list of files Leo Prikler
2019-12-15 22:26   ` Brett Gilio
2019-12-15 23:01     ` Leo Prikler
2019-12-15 23:18       ` Brett Gilio
2019-12-17  5:03       ` Maxim Cournoyer
2019-12-24  0:31         ` Brett Gilio
2019-12-27  5:06           ` Maxim Cournoyer
2019-12-27 23:07             ` Brett Gilio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tv62itdl.fsf@posteo.net \
    --to=brettg@posteo.net \
    --cc=38613@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).