unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* Question about package dependencies from github
@ 2023-01-13 11:11 Daniel Fleischer
  2023-01-13 11:16 ` Jean Louis
  0 siblings, 1 reply; 2+ messages in thread
From: Daniel Fleischer @ 2023-01-13 11:11 UTC (permalink / raw)
  To: help-gnu-emacs

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Question about package dependencies from github
  2023-01-13 11:11 Question about package dependencies from github Daniel Fleischer
@ 2023-01-13 11:16 ` Jean Louis
  0 siblings, 0 replies; 2+ messages in thread
From: Jean Louis @ 2023-01-13 11:16 UTC (permalink / raw)
  To: Daniel Fleischer; +Cc: help-gnu-emacs

* 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/



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-01-13 11:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-13 11:11 Question about package dependencies from github Daniel Fleischer
2023-01-13 11:16 ` Jean Louis

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).