all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: A few NonGNU ELPA package proposals
Date: Sun, 03 Jul 2022 22:35:16 +0000	[thread overview]
Message-ID: <875ykdn7tn.fsf@posteo.net> (raw)
In-Reply-To: Philip Kaludercic's message of "(unknown date)"

Philip Kaludercic <philipk@posteo.net> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>>> >> Hope there are no objections to these additions.
>>>> > What are the criteria for objections in this case?
>>>> If someone thinks that there are technical issues with the package
>>> What kind of technical issues would be relevant in these cases?
>>
>> E.g. if one of those packages depends on a package which is not in
>> (Non)GNU ELPA?

Yes, or something like deprecated dependencies that can be fixed, in
case I missed something.

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> there is a better alternative to some package I propose that we
>>> should add instead of what I suggested to avoid duplication.
>>
>> This last criterion I don't think I understand.  I was under the
>> impression that we are not supposed to limit admission of packages
>> just because there are alternatives to what they do.
>>
>> For example, symbol-overlay seems to do what hi-lock-mode does.  But
>> my understanding was that this fact shouldn't preclude symbol-overlay
>> from being admitted.  Now you seem to be saying that we shouldn't add
>> such packages?
>>
>> Bottom line: I'm still confused.

To my knowledge these aren't fixed rules, and as I say "avoid" doesn't
mean prevent by all means.  There are already examples like project and
projectile that are pretty similar.  In this case it seems to me that
symbol-overlay is sufficiently different from hi-lock-mode to make the
addition worthwhile, but of course that is exactly the point I wanted to
discuss.

The general intention is to allow for comments before adding new
packages.



  parent reply	other threads:[~2022-07-03 22:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 10:12 A few NonGNU ELPA package proposals Philip Kaludercic
2022-07-01 10:37 ` Eli Zaretskii
2022-07-01 13:16   ` Philip Kaludercic
2022-07-01 13:27     ` Eli Zaretskii
2022-07-01 14:42       ` Stefan Monnier
2022-07-03 22:35       ` Philip Kaludercic [this message]
2022-07-06  7:09         ` Bozhidar Batsov
2022-07-07 15:29           ` Philip Kaludercic

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=875ykdn7tn.fsf@posteo.net \
    --to=philipk@posteo.net \
    --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 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.