unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: documentation incorrect for function `define-package'?
Date: Sat, 25 Sep 2021 11:51:01 -0700	[thread overview]
Message-ID: <CADwFkmk7J4azgrO5butiMKitywCaEfifrKzT5_hnT3podnaZfw@mail.gmail.com> (raw)
In-Reply-To: <87pmswr0a5.fsf@gmail.com>

Michelangelo Rodriguez <michelangelo.rodriguez@gmail.com> writes:

> So, in my actual understanding of how the package system works, actually
> <package>-pkg.el is generated by an authomation when that package is
> installed from elpa or another archive?

It is generated by whatever software creates the package archive.

GNU ELPA and MELPA are two notable examples.

> I think that because i try to install a local package in which i'm
> working and if i try to install it by using `package-install-file' and i
> don't specify various keywords to `define-package' then
> `describe-package' does'nt report correctly some information.
> so, which is the "correct way " to test the package?

In general, you shouldn't need to create this file yourself.  It will be
created for you by e.g. GNU ELPA.  What you do need to do is ensure that
your package headers are correct.

The usual work-flow here, I think, is to add your package to a package
archive, see what kind of metadata it comes up with and address any
problems you see.



  reply	other threads:[~2021-09-25 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 14:16 documentation incorrect for function `define-package'? Michelangelo Rodriguez
2021-09-24 15:01 ` Stefan Kangas
2021-09-25 18:13   ` Michelangelo Rodriguez
2021-09-25 18:51     ` Stefan Kangas [this message]
2021-09-25 21:48       ` Michelangelo Rodriguez

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=CADwFkmk7J4azgrO5butiMKitywCaEfifrKzT5_hnT3podnaZfw@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=michelangelo.rodriguez@gmail.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 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).