unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Uwe Brauer <oub@mat.ucm.es>,
	Philip Kaludercic <philipk@posteo.net>,
	Andrea Corallo <acorallo@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: having emacs-matlab in ELPA, finally. FSF paper signed
Date: Sun, 24 Nov 2024 09:16:53 +0100	[thread overview]
Message-ID: <87jzct11xm.fsf@mat.ucm.es> (raw)
In-Reply-To: CADwFkmmVNYrZGfMq95VS0M60E9u+_sdJjEPFpLpqKrsxrVGn=Q@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 3002 bytes --]

>>> "SK" == Stefan Kangas <stefankangas@gmail.com> writes:

> Uwe Brauer <oub@mat.ucm.es> writes:
>>>>> "SK" == Stefan Kangas <stefankangas@gmail.com> writes:
>> 
>>> Philip Kaludercic <philipk@posteo.net> writes:
>>> +(defconst matlab-mode-version (package-get-version)
>>> +  "Current version of MATLAB(R) mode.")
>> 
>>> We have tried to discourage the addition of such variables and commands,
>>> given that one can always find that information by other means,
>>> e.g. interactively with `describe-package` or from Lisp:
>> 
>>> (package-desc-version (cadr (assq 'foo package-alist)))
>> 
>> So you want me use just that string
>> well (package-desc-version (cadr (assq 'matlab-mode package-alist)))
>> I presume
>> 
>> in matlab.el (and matlab-mode.el)?

> That's what I would do, indeed.  Well, I'd use this if you need the
> string form:

>     (package-version-join
>      (package-desc-version (cadr (assq 'matlab-mode package-alist))))

Just to be sure, in both files, matlab.el and and matlab-mode.el?



>> What's about our current setting
>> 
>> (defconst matlab-mode-version "6.2"
>> "Current version of MATLAB(R) mode.")
>> 
>> Which we need for MELPA?

> Hmm, are you sure that you need it for MELPA even with the addition of
> the "Version" header?

> In any case, this is an extremely minor nit either way.


Ok, a last question then, as Philip wrote 

,----
| * As soon as it works.  The main issues right now, are as you noticed
|   that ELPA doesn't release a new tarball for every commit, but just
|   when a new version is released.  We track this by checking for commits
|   that bump the "Version" header in the main file (in your case
|   matlab.el).  You currently don't have any version number, so the build
|   fails.  I would suggest applying a change like this, if it doesn't
|   break any assumptions you have regarding the minimal Emacs version:
`----

But what is meant by «bump the Version header"
since this header somehow seems to be determined by 
     (package-version-join
      (package-desc-version (cadr (assq 'matlab-mode package-alist))))

But if I run eval-sexep this returns 
"20191223.2012"


So I don't see any place where I manually change the Version header. Or
are we talking about adding a (git) tag?

I guess I need something  like this (stolen from auctex, who BTW use 😉
,----
| (defconst AUCTeX-version (package-get-version)
|   "AUCTeX version.")
`----


;;; matlab.el --- major mode for MATLAB(R) dot-m files -*- lexical-binding: t -*-

;; Copyright (C) 2014-2024 Free Software Foundation, Inc.

;; Version: 6.2
;; URL: https://www.gnu.org/software/auctex/
;; Author: Matt Wette <mwette@alumni.caltech.edu>,
;;         Eric M. Ludlam <eludlam@mathworks.com>
;; Maintainer: Uwe Brauer <oub@mat.ucm.es>,
;;             Eric M. Ludlam  <eludlam@mathworks.com> 
;; Package-Requires: ((emacs "27.1"))
;; Created: 04 Jan 91
;; Keywords: MATLAB(R)


Uwe 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5684 bytes --]

  reply	other threads:[~2024-11-24  8:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 12:45 having emacs-matlab in ELPA, finally. FSF paper signed Uwe Brauer
2024-08-06 21:55 ` Andrea Corallo
2024-08-07 17:03   ` Uwe Brauer
2024-08-07 17:54     ` Andrea Corallo
2024-08-12 11:20     ` Philip Kaludercic
2024-08-12 11:33       ` Andreas Schwab
2024-08-12 11:38         ` Philip Kaludercic
2024-08-12 12:16       ` Uwe Brauer
2024-08-12 12:29         ` Philip Kaludercic
2024-08-12 14:58           ` Uwe Brauer
2024-08-12 15:06             ` Philip Kaludercic
2024-08-12 15:17               ` Uwe Brauer
2024-08-12 16:11                 ` Philip Kaludercic
2024-11-22 16:12           ` Uwe Brauer
2024-11-23 10:30             ` Philip Kaludercic
2024-11-23 12:07               ` Stefan Kangas
2024-11-23 13:22                 ` Uwe Brauer
2024-11-23 19:13                   ` Stefan Kangas
2024-11-24  8:16                     ` Uwe Brauer [this message]
2024-11-24 11:12                       ` Stefan Kangas
2024-11-24 14:07                         ` Uwe Brauer
2024-11-24 19:59                     ` Philip Kaludercic
2024-11-24 20:37                       ` Uwe Brauer
2024-11-24 21:34                         ` Philip Kaludercic
2024-11-25  7:37                           ` Uwe Brauer via Emacs development discussions.
2024-11-25  7:45                           ` Uwe Brauer via Emacs development discussions.
2024-11-23 13:19               ` Uwe Brauer via Matlab-emacs-discuss
2024-11-23 13:30               ` having emacs-matlab in ELPA, finally. FSF paper signed, " Uwe Brauer

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=87jzct11xm.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=stefankangas@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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