all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] externals/firefox-javascript-repl 056b687af4 2/3: Work around missing submodule support in GNU ELPA
Date: Mon, 05 Jun 2023 09:15:02 -0400	[thread overview]
Message-ID: <m3zg5erqy1.fsf@fitzsim.org> (raw)
In-Reply-To: <875y82axg8.fsf@posteo.net> (Philip Kaludercic's message of "Mon,  05 Jun 2023 12:46:31 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

> Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:
>
>> branch: externals/firefox-javascript-repl
>> commit 056b687af4d70252dee2cdd2323da3990fabd558
>> Author: Thomas Fitzsimmons <fitzsim@fitzsim.org>
>> Commit: Thomas Fitzsimmons <fitzsim@fitzsim.org>
>>
>>     Work around missing submodule support in GNU ELPA
>
> What do you need to do?

Package deployment needs to (at least):

cd elpa/packages/firefox-javascript-repl
git submodule update --init

before building the package, so that wtfjs/README.md is available for
inclusion in the tarball.  Maybe "make worktrees" could also initialize
submodules.

I'm OK with the current workaround though, if supporting submodules is a
lot of work.

Thanks,
Thomas



      reply	other threads:[~2023-06-05 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168565525463.8048.4344900670894070114@vcs2.savannah.gnu.org>
     [not found] ` <20230601213415.21F57C21A9F@vcs2.savannah.gnu.org>
2023-06-05 12:46   ` [elpa] externals/firefox-javascript-repl 056b687af4 2/3: Work around missing submodule support in GNU ELPA Philip Kaludercic
2023-06-05 13:15     ` Thomas Fitzsimmons [this message]

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

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

  git send-email \
    --in-reply-to=m3zg5erqy1.fsf@fitzsim.org \
    --to=fitzsim@fitzsim.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.