all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Philip Kaludercic <philipk@posteo.net>
Cc: "Daniel Mendler" <mail@daniel-mendler.de>,
	"Iñigo Serna" <inigoserna@gmx.com>, tumashu <tumashu@163.com>,
	emacs-devel@gnu.org
Subject: Re: [ELPA] New package: vertico-posframe
Date: Tue, 26 Oct 2021 14:19:19 -0400	[thread overview]
Message-ID: <jwv4k93y7hj.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87pmrrk9vl.fsf@posteo.net> (Philip Kaludercic's message of "Tue,  26 Oct 2021 16:51:10 +0000")

Philip Kaludercic [2021-10-26 16:51:10] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Indeed, the packages should not be bundled together.  vertico-posframe is
>>> an independent component, which pulls in a third-party dependency.
>>
>> I don't have an opinion on how those should be packaged, but I'll just
>> point out that Vertico would not needed to have `posframe` in its
>> `Package-Requires` in order to provide support for Posframe.
>
> Yes, this was what I was thinking about. A soft dependency that would
> raise an error of the posframe part were actually required, but would
> otherwise ignore it.
>
> But as Daniel has said he prefers not to do it this way, we can add
> vertico-posframe as a separate package.

Yes, either way is fine.


        Stefan




  reply	other threads:[~2021-10-26 18:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25  3:06 [ELPA] New package: vertico-posframe tumashu
2021-10-25 16:13 ` Philip Kaludercic
2021-10-26  0:45   ` tumashu
2021-10-26  7:25     ` Iñigo Serna
2021-10-26  7:35       ` Daniel Mendler
2021-10-26 12:00         ` Stefan Monnier
2021-10-26 16:51           ` Philip Kaludercic
2021-10-26 18:19             ` Stefan Monnier [this message]
2021-10-26  9:12     ` Philip Kaludercic
2021-10-27 18:00       ` Philip Kaludercic
2021-10-28  9:12         ` tumashu

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=jwv4k93y7hj.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=inigoserna@gmx.com \
    --cc=mail@daniel-mendler.de \
    --cc=philipk@posteo.net \
    --cc=tumashu@163.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.