Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Wolfgang Mederle <walthervondervogelweide@gmx.de>
Newsgroups: comp.emacs
Subject: derive from an Emacs package without modifying it
Date: Thu, 11 Sep 2025 19:03:38 +0200
Organization: Die Bande, in die alle wollen
Lines: 19
Message-ID: <87cy7w6hw5.fsf@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain
X-Trace: individual.net 2wZzOOBjwzdYymzZD5OPFwNSjeGe+7s/de9GtBJqLrxlvWv7dy
Cancel-Lock: sha1:83kk37E7s2Vv5WvKgQJY7jux9hI= sha1:qji9lOqt8u1kABpdz+2ReVibklM= sha256:veBK/wrtNt3aaS1NHdrf6c6TOYpZMMxlo6u9yzbO7+g=
User-Agent: Gnus/5.13 (Gnus v5.13)
X-Spam: No
Xref: csiph.com comp.emacs:2477

I have for years been using the ejira package to access Jira from Emacs.
A recent change in the Jira API prompted me to update my fork of the
package for Jira API v3. In order for this to work, I needed to also
update the dependencies jiralib2 and ox-jira.

Since these package updates might be useful for others, I want to
provide them, ideally even via Melpa. But: I have a couple of extensions
in ejira that are only working in my employer's Jira configuration.

My question is, how do I mitigiate these requirements? The changes are
e. g. in a core defstruct of ejira. I would have to change these back to
default in order to make ejira3 useful to others. So, what do with the
changes I still need for my own workflow? Should I add those into a
second package to be loaded after ejira was initialized?

Any suggestions appreciated.

Cheers,
Wolfgang