From: Philip Kaludercic <philipk@posteo.net>
To: dalanicolai <dalanicolai@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Why 'define-package' marked obsolete?
Date: Mon, 20 Mar 2023 16:58:11 +0000 [thread overview]
Message-ID: <87bkkn9x7g.fsf@posteo.net> (raw)
In-Reply-To: <CACJP=3m6HRy8PRMnUxuMyBYJcW1q1H5K3_5HnUgbhnO4MDCQoQ@mail.gmail.com> (dalanicolai@gmail.com's message of "Mon, 20 Mar 2023 17:21:04 +0100")
dalanicolai <dalanicolai@gmail.com> writes:
> HI all!
>
> Can I ask why 'define-package' was marked obsolete?
> I can not find any information about it. I have searched the log,
> where I could only find the respective commit
> <https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=ade7a212a882540178d9504e7e0bd3be3bf1fd41>
> .
>
> I have also searched the Emacs news for versions 28, 29 and 30,
> but also there, I can find no information.
>
> Also in the comments of package.el itself I can not find any information
> about it.
>
> Is it documented anywhere?
`Define-package' is not an expression that is to be evaluated, it is
just a (backwards-compatible) formatting for -pkg.el files. If you take
a look at `package-process-define-package' and
`package-load-descriptor', you will see that the arguments are actually
passed to `package-desc-from-define' which is a `package-desc'
constructor.
AFAIU the changes you are interested in where made in the commit
a7270fb20feaedc5dc6c4e0936714bdb167062f7.
> Thanks!
--
Philip Kaludercic
next prev parent reply other threads:[~2023-03-20 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 16:21 Why 'define-package' marked obsolete? dalanicolai
2023-03-20 16:58 ` Philip Kaludercic [this message]
2023-03-20 17:15 ` Eli Zaretskii
2023-03-20 19:32 ` Philip Kaludercic
2023-03-21 9:10 ` dalanicolai
2023-03-21 9:36 ` Philip Kaludercic
2023-03-21 17:09 ` dalanicolai
2023-03-21 17:15 ` Philip Kaludercic
2023-03-22 21:27 ` dalanicolai
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkkn9x7g.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=dalanicolai@gmail.com \
--cc=emacs-devel@gnu.org \
/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 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).