From: Philip Kaludercic <philipk@posteo.net>
To: "Kjartan Óli Águstsson" <kjartanoli@outlook.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: calibre.el
Date: Thu, 20 Apr 2023 18:26:42 +0000 [thread overview]
Message-ID: <87h6ta2yvx.fsf@posteo.net> (raw)
In-Reply-To: <GV1P193MB2310A2209D24B259B7EA4399DF9D9@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM> ("Kjartan Óli Águstsson"'s message of "Tue, 18 Apr 2023 08:19:59 +0000")
Kjartan Óli Águstsson <kjartanoli@outlook.com> writes:
>>> 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.
It is a common mistake or a MELPA-ism I don't know about ^^.
> As for the usage of eieio, is there a reason not to use it?
If you just need a structure then cl-defstruct should be a less-heavy
solution.
next prev parent reply other threads:[~2023-04-20 18:26 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
2023-04-20 13:37 ` dalanicolai
2023-04-20 19:28 ` Kjartan Óli Águstsson
2023-04-20 18:26 ` Philip Kaludercic [this message]
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=87h6ta2yvx.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=kjartanoli@outlook.com \
/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.