From: "Kjartan Óli Águstsson" <kjartanoli@outlook.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: calibre.el
Date: Tue, 18 Apr 2023 08:19:59 +0000 [thread overview]
Message-ID: <GV1P193MB2310A2209D24B259B7EA4399DF9D9@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87v8ht3etv.fsf@posteo.net>
Thank you for taking the time to look at it.
>> Would there be any
>> interest in adding it to GNU ELPA? And if so, is my copyright assignment
>> for Emacs sufficient, or does ELPA require a separate assignment?
>
> No separate assignment is necessary, as GNU ELPA packages are regarded
> to be part of Emacs.
Good to know.
>> This is my first attempt at writing an Emacs package, so I expect to
>> have gotten many things wrong. As such I would welcome reviews from
>> people who know more about Elisp packaging.
>
> The first thing to note is that you don't need a -pkg.el file. ELPA
> will generate one for you using the metadata in the main file and
> overwrite whatever you have written.
Another good to know. I remember reading that somewhere, but then I
looked at some other packages that seemed to maintain a -pkg.el file.
> This means you should copy the metadata to calibre.el. Especially the
> dependency list. (Also, why do you depend on "29.1.0", a version which
> is unreleased and has an additional ".0" at the end? I guess you need
> Emacs 29 because of SQLite? Have you taken a look at emacsql?)
I'll definitely fix the .0 thing. You are correct that the dependency
on Emacs 29 is for SQLite. Emacsql would not work, since I am
interacting with an existing database maintained by Calibre. If you
want to wait until Emacs 29 is released to add it I would definitely
agree to that.
> From a brief skim of the code, it looks more or less fine. There are
> minor things I am not sure about (such as the usage of eieio or why you
> declare some functions instead of requiring the file).
The functions that are declared instead of required currently cause a
recursive require because of how the package is structured. I am hoping
to refactor this soon.
As for the usage of eieio, is there a reason not to use it?
--
Kjartan Oli Agustsson
GPG Key fingerprint: 4801 0D71 49C0 1DD6 E5FD 6AC9 D757 2FE3 605E E6B0
next prev parent reply other threads:[~2023-04-18 8:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 23:23 [ELPA] New package: calibre.el Kjartan Óli Águstsson
2023-04-18 6:05 ` Philip Kaludercic
2023-04-18 8:19 ` Kjartan Óli Águstsson [this message]
2023-04-20 13:37 ` dalanicolai
2023-04-20 19:28 ` Kjartan Óli Águstsson
2023-04-20 18:26 ` Philip Kaludercic
2023-04-20 19:46 ` Kjartan Óli Águstsson
2023-05-09 12:50 ` Kjartan Óli Águstsson
2023-05-10 6:36 ` Philip Kaludercic
2023-05-10 11:24 ` Eli Zaretskii
2023-05-10 12:34 ` Kjartan Óli Águstsson
2023-05-16 19:38 ` Philip Kaludercic
2023-05-17 15:01 ` Kjartan Óli Águstsson
2023-05-18 13:01 ` Philip Kaludercic
2023-05-18 16:23 ` Kjartan Óli Águstsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=GV1P193MB2310A2209D24B259B7EA4399DF9D9@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM \
--to=kjartanoli@outlook.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.