unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Distopico <distopico@riseup.net>
Cc: emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New package: flymake-guile
Date: Tue, 05 Sep 2023 16:01:44 +0000	[thread overview]
Message-ID: <87wmx4ehhz.fsf@posteo.net> (raw)
In-Reply-To: <87wmx4k611.fsf@riseup.net> (distopico@riseup.net's message of "Tue, 05 Sep 2023 10:09:50 -0500")

Distopico <distopico@riseup.net> writes:

> On 2023-09-05, Philip Kaludercic <philipk@posteo.net> wrote:
>
>> Distopico <distopico@riseup.net> writes:
>>
>>> Hi Philip,
>>>
>>> On 2023-09-01, Philip Kaludercic <philipk@posteo.net> wrote:
>>>
>>>>>>>
>>>>>>> flymake-collection use an adaptation of flymake-quickdef[1], that is
>>>>>>> a macro similar to the quickdef one[2], could be use quickdef a blocker
>>>>>>> to add the package on NonGNU ELPA?
>>>>>>
>>>>>> I am afraid I don't understand your question.
>>>>>
>>>>> My Question is if remove flymake-quickdef as dependency is a requirement
>>>>> to merge flymake-guile package into NonGNU ELPA or it's just a
>>>>> recommendation?   
>>>>
>>>> It is a strong recommendation.  FWIW I have done the work of
>>>> macroexpanding and cleaning the resulting code up (but there is still
>>>> some more work to be done), and you can see what I had in mind:
>>>>
>>>
>>> I just made those change in the repo, you can check those now:
>>> https://framagit.org/flymake-backends/flymake-guile, and BTW I added
>>> `.elpaignore`, attache the patch adding just `flymake-guile`.
>>
>> Great, thank you very much.  I'll push the changes to nongnu.git.  Are
>> you otherwise familiar with the process of how ELPAs work?
>
> Thank you,

No problem :)

> About the process I'm not sure about it, how I publish a
> new version? I guess is just update version in the repo but not sure
> if I need to do something more  

No, all you need to do is to bump the version tag in the package header,
and that commit will be used to create a new release tarball.  You can
also check out the NonGNU ELPA package guidelines[0], but I don't assume
there should be any issues here wrt non-free dependencies, since Guile
is firmly free software.

If you change anything and want to see how the ELPA build server handled
the change without triggering a release, you can check the "NonGNU
ELPA-devel" repository, that creates a new release for each individual
commit: https://elpa.nongnu.org/nongnu-devel/.

[0] https://git.savannah.gnu.org/cgit/emacs/nongnu.git/tree/README.org#n118



  reply	other threads:[~2023-09-05 16:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  2:23 [NonGNU ELPA] New package: flymake-guile Distopico
2023-08-31  6:31 ` Stefan Kangas
2023-08-31 16:03   ` Distopico
2023-08-31  6:52 ` Philip Kaludercic
2023-08-31 16:08   ` Distopico
2023-08-31 18:02     ` Philip Kaludercic
2023-08-31 19:22       ` Distopico
2023-09-01 13:09         ` Philip Kaludercic
2023-09-01 13:45           ` Dr. Arne Babenhauserheide
2023-09-01 13:52             ` Philip Kaludercic
2023-09-01 13:58           ` Distopico
2023-09-01 14:23             ` Philip Kaludercic
2023-09-05  2:23               ` Distopico
2023-09-05  7:08                 ` Philip Kaludercic
2023-09-05 15:09                   ` Distopico
2023-09-05 16:01                     ` Philip Kaludercic [this message]
2023-09-05 16:03                       ` Distopico
2023-08-31 11:03 ` Mauro Aranda
2023-08-31 16:13   ` Distopico
2023-08-31 16:15 ` Distopico

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=87wmx4ehhz.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=distopico@riseup.net \
    --cc=emacs-devel@gnu.org \
    /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).