From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 22055-done@debbugs.gnu.org
Subject: bug#22055: Some Elpa packages don't provide a feature
Date: Sat, 12 Dec 2015 20:34:53 +0000 [thread overview]
Message-ID: <CAAdUY-+Y4=_q93gyKVjx5Jmfb9ZLXfinXK4a_+6nEdLcL5OKwg@mail.gmail.com> (raw)
In-Reply-To: <87bn9vzcgc.fsf@bernoul.li>
Closing the bug then.
2015-12-12 19:36 GMT+00:00 Jonas Bernoulli <jonas@bernoul.li>:
>
> Artur Malabarba <bruce.connor.am@gmail.com> writes:
>
>> 2015-12-03 14:34 GMT+00:00 Jonas Bernoulli <jonas@bernoul.li>:
>>>
>>> Artur Malabarba <bruce.connor.am@gmail.com> writes:
>>>
>>>>> `load-relative' also doesn't provide its feature using `provide', but
>>>>> that is intentional - it uses the alternative `provide-me' form, which
>>>>> it itself defines.
>>>>
>>>> I can't see the benefit but I also can't see the harm. Did it affect you
>>>> negatively in any way?
>>>
>>> No, I just cannot mirror it on the Emacsmirror, but that does not really
>>> matter because I also could not mirror any other package which uses
>>> `provide-me'. I extract metadata for all mirrored packages, including
>>> the provided features, and the respective code does not support
>>> `provide-me'. I don't intend to support that form until at least halve
>>> a dozen packages use it.
>>
>> Well, I couldn't find a package Gelpa or Melpa that uses it. So I
>> think it's not really a big deal either way. =P
>
> Yeah, I'll deal with it when the need arises.
prev parent reply other threads:[~2015-12-12 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 19:34 bug#22055: Some Elpa packages don't provide a feature Jonas Bernoulli
2015-11-30 9:57 ` Artur Malabarba
2015-12-03 14:34 ` Jonas Bernoulli
2015-12-03 15:41 ` Artur Malabarba
2015-12-12 19:36 ` Jonas Bernoulli
2015-12-12 20:34 ` Artur Malabarba [this message]
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='CAAdUY-+Y4=_q93gyKVjx5Jmfb9ZLXfinXK4a_+6nEdLcL5OKwg@mail.gmail.com' \
--to=bruce.connor.am@gmail.com \
--cc=22055-done@debbugs.gnu.org \
--cc=jonas@bernoul.li \
/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.