unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Daniel Fleischer <danflscr@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Question about package dependencies from github
Date: Fri, 13 Jan 2023 14:16:47 +0300	[thread overview]
Message-ID: <Y8E9nzW5aUpaOCNO@protected.localdomain> (raw)
In-Reply-To: <m2pmbieljm.fsf@gmail.com>

* Daniel Fleischer <danflscr@gmail.com> [2023-01-13 14:13]:
> 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?

How I see it, you should read this:

(info "(elisp) Packaging Basics")

And then use

(require 'other-package-1)
(require 'other-package-2)

and that is all.

You should not make your package download other packages, that is
something you leave to users. 

Or as another option:
---------------------

You are free to mix other people's works in your work, as long as you
comply with free licenses. In that case you do not need to make
dependencies on other people's packages.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



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

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

  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=Y8E9nzW5aUpaOCNO@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=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).