unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: dalanicolai <dalanicolai@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: Why 'define-package' marked obsolete?
Date: Tue, 21 Mar 2023 09:36:07 +0000	[thread overview]
Message-ID: <87355y78fs.fsf@posteo.net> (raw)
In-Reply-To: <CACJP=3=1A8X42W4WrVmrSeBBbNjvZCS-fyecpBhs2KD6AWDEdA@mail.gmail.com> (dalanicolai@gmail.com's message of "Tue, 21 Mar 2023 10:10:02 +0100")

dalanicolai <dalanicolai@gmail.com> writes:

> Ah okay, I see.
>
> So I assume that this means that as a function 'define-package' was
> redundant, but we should still include a 'define-package' in the
> -pkg.el file of a multi file package?

No, the -pkg.el file is generated by ELPA using the information from the
main file.  There is no need to write it yourself, in fact it is a waste
effort since it will be overwritten anyway.  Package-vc does the same
btw.

> The initial comment of 'package.el' mentions that the -pkg.el file
> should consist of 'a call to' define-package. I would say this
> formulation is somewhat confusing/misleading then?

You are right, that comment is outdated and should be revised.

> Or is the -pkg.el file just outdated? And did I miss the news about it?

No, the file is still required because it contains the package
descriptor.  The only thing that changed is that instead of the contents
being evaluated as code, they are read in and processed manually.
Without that file, you will notice that `package-load-descriptor'
wouldn't add the package to `package-alist', which in turn means that
`package--activate-all' wouldn't activate it.

> On Mon, 20 Mar 2023 at 20:32, Philip Kaludercic <philipk@posteo.net> wrote:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> From: dalanicolai <dalanicolai@gmail.com>
>> >> Date: Mon, 20 Mar 2023 17:21:04 +0100
>> >>
>> >> Can I ask why 'define-package' was marked obsolete?
>> >
>> > It never did anything useful.  Its original implementation just
>> > signaled an error.
>>
>> I just looked up the definition from when package.el was merged[0], and it
>> did stuff, mainly modifying `package-alist'.
>>
>> [0]
>> https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/emacs-lisp/package.el?id=44198b6ee97bcb0ac88a5cadd1bf9b62048d0156#n513
>>
>> --
>> Philip Kaludercic
>>



  reply	other threads:[~2023-03-21  9:36 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
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 [this message]
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=87355y78fs.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=dalanicolai@gmail.com \
    --cc=eliz@gnu.org \
    --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).