Re: Changes to make in elpa-packages file for nongnu elpa

[Philip Kaludercic]

Thierry Volpiatto <thievol@posteo.net> writes:

> I see that Helm installation from nongnu elpa doesn't include
> emacs-helm.sh script, would it be possible to modify this?
>
>         diff --git a/elpa-packages b/elpa-packages
>         index 77d7a5409e..0923724b62 100644
>         --- a/elpa-packages
>         +++ b/elpa-packages
>         @@ -312,11 +312,11 @@
>            :ignored-files "COPYING")
>          
>           (helm                       :url 
> "https://github.com/emacs-helm/helm";
>         -  :ignored-files ("images" "Cask" "Makefile" "emacs-helm.sh" 
> "helm-core.el" "helm.el"
>         +  :ignored-files ("images" "Makefile" "helm-core.el" "helm.el"
>                         "helm-lib.el" "helm-source.el" "helm-multi-match.el"))
>          
>           (helm-core          :url "https://github.com/emacs-helm/helm";
>         -  :ignored-files ("images" "Cask" "Makefile" "emacs-helm.sh" 
> "helm-adaptive.el"
>         +  :ignored-files ("images" "Makefile" "emacs-helm.sh" 
> "helm-adaptive.el"
>                         "helm-bookmark.el" "helm-buffers.el" "helm-color.el" 
> "helm-comint.el"
>                         "helm-command.el" "helm-config.el" "helm-dabbrev.el" 
> "helm-easymenu.el"
>                         "helm-elisp.el" "helm-elisp-package.el" "helm-epa.el" 
> "helm-eshell.el"

There shouldn't be any issue in applying this patch, but could you
explain the propose of this script?  I see something involving
straight.el, which is a package.el-incompatible package manager, at
which point I am confused why this should be distributed along with a
"package.el"-package.

> Also I asked here about a new dependency for Helm called wfnames and had
> no answer (2 times), 

Sorry about that, you can always feel free to CC me if you have specific
questions that might get lost on the mailing list.  I suppose Stefan
Monnier wouldn't object to be mentioned either.

>                      so I ask again differently now:
>
> When a package is available in Melpa do we have to add it in nongnu as
> well to satisfy dependencies for a package already in nongnu?

Yes, if the dependency is missing someone only using GNU ELPA and NonGNU
ELPA wouldn't be able to install the package due to a missing dependency
and that is obviously not intended.

> Thanks.