> Uwe Brauer <oub@mat.ucm.es> writes:

> Packages usually don't have to deal with that, all the ELPA build system
> needs is a git repository URL, and that is usually enough to figure out
> the rest.  If it uses some unconventional branch name that is not
> default, we just need to note that in the package specification.

Ok


> So this is the host: https://sourceforge.net/projects/matlab-emacs/?

Aeh, well yes and no. This is, still the main repository for your
development. But lately, especially the authors working for matlab,
would  like to move the main development to github, because of its
interface, pull requests etc (I am not a huge fan though 😬).

But before we move I would like to clean up the repository a bit,
deleting obsolete branches, rebasing this sort of things, and there is
still a branch, not merged with master whose status is unclear.

The next thing is then to check the headers of the files etc.

An issue that worries me is this. If out of a sudden a lot of new
contributions pop up, then I have to think of having a separate branch,
say called ELPA in which all authors have signed the FSF papers and
main/default the main development branch. I have still not made my mine


> IIRC MELPA forces contributors to write their own package
> specifications, right?

Yes a so called recipy files and then you have to do a pull request,
sigh 😬

>   Some people do that for ELPA, but it is not
> expected (I usually find it easier to update elpa.git myself).  In this
> case, the basic specification is just:

> diff --git a/matlab-shell.el b/matlab-shell.el
> index ee80555bee..07c6223137 100644
> --- a/matlab-shell.el
> +++ b/matlab-shell.el
> @@ -1003,7 +1003,7 @@ Sends commands to the MATLAB shell to initialize the MATLAB process."
>  	     (ecca (if ecc (format "emacs.set('clientcmd', '%s');" ecc) ""))
>  	     (args (list nsa ecca))
>  	     (cmd (format "run('%s');%s" initcmd (apply 'concat args))))
> -	(matlab-shell-send-command cmd)
> +	(matlab-shell-send-command (string-replace (expand-file-name "~/") "~/" cmd))
>  	)
     
>      ;; Setup is misconfigured - we need emacsinit because it tells us how to debug

Thanks I will have look later

> Though right now the package doesn't build, as the package is not well
> formed according to (elisp) Packaging.  Among other things, it lacks a
> "Version" header.

Yes, I know on my TODO list, but I want to finish the cleanup process fist




-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine.