Re: Making AUCTeX ELPA releases from the master branch

[Tassilo Horn]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> So just that I get it right, we'd do:
>>
>>   - Make our former externals/elpa branch the new main branch
>>     - git checkout -b main externals/elpa && git push
>>   - Then clone elpa and setup the infrastructure as you said
>>   - Edit elpa-packages locally (but don't yet commit/push)
>>     - remove `:manual-sync t`
>>     - add `:branch "main"` and maybe `:make "elpa"`
>>   - Then "make packages/auctex" once
>>   - while (make auctex.tar is not satisfactory)
>>     - edit on our new main branch, e.g., refine the elpa target
>>   - commit and push the modifications to the auctex recipe in
>>     elpa-packages
>
> Pretty much, yes.
>
> Note that `make auctex.tar` doesn't care about branches and remote
> repositories, it just takes the commit currently found in
> `packages/auctex` and makes a tarball from it (IOW things like `:url`,
> `:manual-sync`, and `:branch` aren't used in the recipe, tho the rest
> is).

So I could just replace packages/auctex with some other clone of
auctex.git?

> So your first and third steps above can happen at some other time.

Alright.  But I currently don't understand how "make packages/auctex"
knows which commit to check out.  I mean, the elpa-packages auctex
recipe has auctex.git as :url but auctex.git doesn't contain the
externals/auctex branch but only elpa.git does.  And nowhere in the elpa
repository do I find some statement that for auctex the externals/auctex
branch in elpa.git is to be used instead of the main or master branch of
auctex.git.  Is there some general rule that a package foo will be built
from the HEAD of the externals/foo elpa.git branch if such a branch
exists discarding what's specified as `:url` and `:branch` in the foo
package recipe?

Bye,
Tassilo

[1] It just occurred to me that in all mails I've written about an
    externals/elpa branch which is actually externals/auctex.