emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ELPA] new single file package: mpdired.el


From: Manuel Giraud
Subject: Re: [ELPA] new single file package: mpdired.el
Date: Sat, 09 Mar 2024 14:18:19 +0100
User-agent: Gnus/5.13 (Gnus v5.13)

Philip Kaludercic <philipk@posteo.net> writes:

> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
>> Philip Kaludercic <philipk@posteo.net> writes:
>>
>> [...]
>>
>>> OK, this works.  If you have signed the CA, then you could set the
>>> version of your package to some pre-release version, using a
>>
>> I don't know what "signed the CA" means in this context.
>
> Contributing packages to GNU ELPA requires you to have signed the FSF
> copyright assignment, see (info "(emacs) Copyright Assignment"), since
> GNU ELPA packages are formally part of Emacs.  Assuming you haven't done
> so yet, a maintainer can send you the form.

Ok.  So I already have this because I've already contributed to Emacs.

> Git tags aren't needed at all.  The ELPA build server relies entirely on
> what the Version tag says.

Ok, I can still have tags on my side.

>>                                         Just to be sure I understand
>> correctly: every version number with a -pre suffix won't update on ELPA?
>
> Yes, more specifically any version which version-to-list can parse and
> returns a version list without any negative elements:
>
>   (version-to-list "1.0") ;=> (1 0)
>   (version-to-list "1.0pre") ;=> (1 0 -1)
>   (version-to-list "1.0git") ;=> (1 0 -4)
>
> see `version-regexp-alist' and keep in mind that the ELPA build server
> uses a few more extensions.

Thanks, all is clear for me now.
-- 
Manuel Giraud



reply via email to

[Prev in Thread] Current Thread [Next in Thread]