Re: Adding new package to Gnu ELPA with no upstream

[Stephen Leake]

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

>> $ cd c:/Projects/elpa/
>> $ git stash
>> $ git checkout --orphan externals/gpr-mode
>> $ git rm --cached "*"
>> $ git commit --allow-empty -m "new package gpr-mode"
>> $ git checkout -f main
>> # edit elpa-packages - copy from wisi
>> $ git commit -m "new package gpr-mode"
>> $ git push --set-upstream origin externals/gpr-mode
>> $ make packages/gpr-mode
>> # copy files, commit
>> $ cd packages/gpr-mode
>> $ git checkout -b externals-release/gpr-mode
>> $ git push --set-upstream origin externals-release/gpr-mode
>> $ git checkout externals/gpr-mode
>> $ cd c:/Projects/elpa/
>> $ git push
>> $ git stash pop
>
>> Is this worth adding in elpa/README? or is this case rare enough that it
>> will only confuse people?
>
> Maybe a better option is to add a `make fresh/<PKG>` rule that does most
> of the above steps for you (at least for non-release branch, and then
> a subsequent rule to add a release branch)?

That makes sense.

I'll put it on my list, but since I'm done with new packages for a
while, I won't get to it soon.

-- 
-- Stephe