* Best way to sync package versions between Emacs and GNU ELPA?
@ 2020-10-19 9:41 Protesilaos Stavrou
2020-10-21 17:56 ` Kévin Le Gouguec
0 siblings, 1 reply; 4+ messages in thread
From: Protesilaos Stavrou @ 2020-10-19 9:41 UTC (permalink / raw)
To: emacs-devel
The 'modus-operandi' and 'modus-vivendi' themes are included in Emacs.
They also exist as separate/standalone packages on GNU ELPA. The
version in Emacs is 0.13.0, while GNU ELPA currently has 0.12.0. The
packages were available in GNU ELPA before being added to Emacs.
To update GNU ELPA, I have to contact its maintainer and ask them to
fetch the files from my git repository and push them to elpa.git. While
to update the Emacs files, I need to open a bug report and attach a
patch. Please refer to bug#43944 for an example.
My question to the developers: is there some way to reduce the workload
on all sides, while ensuring parity between the two sources?
The three files currently in Emacs that I would like to have in GNU ELPA:
./doc/misc/modus-themes.texi
./etc/themes/modus-operandi-theme.el
./etc/themes/modus-vivendi-theme.el
Please note that each theme is its own package on GNU ELPA, per my
request. Though the new, yet-to-be-synced manual is common between
them.
Thank you in advance for your time.
Best regards,
Protesilaos
--
Protesilaos Stavrou
protesilaos.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Best way to sync package versions between Emacs and GNU ELPA?
2020-10-19 9:41 Best way to sync package versions between Emacs and GNU ELPA? Protesilaos Stavrou
@ 2020-10-21 17:56 ` Kévin Le Gouguec
2020-10-21 21:10 ` Noam Postavsky
0 siblings, 1 reply; 4+ messages in thread
From: Kévin Le Gouguec @ 2020-10-21 17:56 UTC (permalink / raw)
To: Protesilaos Stavrou; +Cc: emacs-devel
Protesilaos Stavrou <info@protesilaos.com> writes:
> My question to the developers: is there some way to reduce the workload
> on all sides, while ensuring parity between the two sources?
IIUC it is possible to keep your package only in emacs.git, and mark it
as a ":core" package in elpa.git[1]. If I'm not mistaken, this makes
releasing a new version on GNU ELPA as simple as bumping the package's
"Version:" tag in emacs.git.
(I've never authored a package so I obviously don't have any first-hand
experience with this. Sorry if I'm making stuff up.)
[1] Search for ":core" in elpa.git/external-list:
http://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/externals-list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Best way to sync package versions between Emacs and GNU ELPA?
2020-10-21 17:56 ` Kévin Le Gouguec
@ 2020-10-21 21:10 ` Noam Postavsky
2020-10-25 7:41 ` Protesilaos Stavrou
0 siblings, 1 reply; 4+ messages in thread
From: Noam Postavsky @ 2020-10-21 21:10 UTC (permalink / raw)
To: Kévin Le Gouguec; +Cc: Protesilaos Stavrou, Emacs developers
On Wed, 21 Oct 2020 at 14:18, Kévin Le Gouguec
<kevin.legouguec@gmail.com> wrote:
>
> Protesilaos Stavrou <info@protesilaos.com> writes:
>
> > My question to the developers: is there some way to reduce the workload
> > on all sides, while ensuring parity between the two sources?
>
> IIUC it is possible to keep your package only in emacs.git, and mark it
> as a ":core" package in elpa.git[1]. If I'm not mistaken, this makes
> releasing a new version on GNU ELPA as simple as bumping the package's
> "Version:" tag in emacs.git.
Also, making a savannah account and asking for write permission to the
git repo will save having to ask someone else to push for you
(although posting a patch can still be useful to get reviews).
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Best way to sync package versions between Emacs and GNU ELPA?
2020-10-21 21:10 ` Noam Postavsky
@ 2020-10-25 7:41 ` Protesilaos Stavrou
0 siblings, 0 replies; 4+ messages in thread
From: Protesilaos Stavrou @ 2020-10-25 7:41 UTC (permalink / raw)
To: Noam Postavsky; +Cc: Emacs developers, Kévin Le Gouguec
On 2020-10-21, 17:10 -0400, Noam Postavsky <npostavs@gmail.com> wrote:
> On Wed, 21 Oct 2020 at 14:18, Kévin Le Gouguec
> <kevin.legouguec@gmail.com> wrote:
>>
>> Protesilaos Stavrou <info@protesilaos.com> writes:
>>
>> > My question to the developers: is there some way to reduce the workload
>> > on all sides, while ensuring parity between the two sources?
>>
>> IIUC it is possible to keep your package only in emacs.git, and mark it
>> as a ":core" package in elpa.git[1]. If I'm not mistaken, this makes
>> releasing a new version on GNU ELPA as simple as bumping the package's
>> "Version:" tag in emacs.git.
>
> Also, making a savannah account and asking for write permission to the
> git repo will save having to ask someone else to push for you
> (although posting a patch can still be useful to get reviews).
Thank you Kevin, Noam! I shall follow your advice.
--
Protesilaos Stavrou
protesilaos.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-10-25 7:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-19 9:41 Best way to sync package versions between Emacs and GNU ELPA? Protesilaos Stavrou
2020-10-21 17:56 ` Kévin Le Gouguec
2020-10-21 21:10 ` Noam Postavsky
2020-10-25 7:41 ` Protesilaos Stavrou
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).