unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Daniel Fleischer <danflscr@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Question about package dependencies from github
Date: Fri, 13 Jan 2023 13:11:41 +0200	[thread overview]
Message-ID: <m2pmbieljm.fsf@gmail.com> (raw)

Hi all, I'm developing a package. It depends on several other packages,
some of them aren't in melpa and/or are my own fork in github with some
modifications. What is the current convention in terms of introducing
them in a package?

I'm using quelpa + use-package in the form of:

(use-package X
   :quelpa (X :fetcher github
              :repo "daniel/X"))

But even without use-package I can have

(quelpa '(X :fetcher github :repo "daniel/X"))

Maybe something else like el-get? Or maybe just put all the packages in
the project as git submodules?

-- 
Daniel Fleischer



             reply	other threads:[~2023-01-13 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 11:11 Daniel Fleischer [this message]
2023-01-13 11:16 ` Question about package dependencies from github Jean Louis

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=m2pmbieljm.fsf@gmail.com \
    --to=danflscr@gmail.com \
    --cc=help-gnu-emacs@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. 
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).