Re: [NonGNU ELPA] New package: flymake-guile

[Distopico <distopico@riseup.net>]

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


On 2023-09-05, Philip Kaludercic <philipk@posteo.net> wrote:

> 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

Cool, thank you

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]