all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Chong Yidong <cyd@gnu.org>
Cc: monnier@IRO.UMontreal.CA, jeremiah.dodds@gmail.com, emacs-devel@gnu.org
Subject: Re: GNU ELPA visibility
Date: Sat, 27 Oct 2012 15:26:36 +0400	[thread overview]
Message-ID: <508BC4EC.3060503@yandex.ru> (raw)
In-Reply-To: <87ip9webn0.fsf@gnu.org>

On 27.10.2012 9:18, Chong Yidong wrote:
> Dmitry Gutov <dgutov@yandex.ru> writes:
>
>>> It would be good if every package would at least complement Version and
>>> Summary with a longer description, a link to its homepage (or emacswiki
>>> page if it has no homepage), and the date when it was updated the last
>>> time.
>>
>> You may find that, for single-file packages, even if they provide an
>> extended "Commentary" section, it will not show up in the
>> "list-packages" interface. At least when distributed over MELPA or
>> Marmalade.
>
> Please provide an example of what you mean.  I just checked with the GNU
> ELPA packages, and the commentaries show up fine with "?" in the
> *Packages* buffer.  Maybe MELPA or Marmalade are not providing the
> *-readme.txt files which are supposed to be there.

That is the problem with those two repositories, yes.

In principle, though, when there is no readme.txt, the package manager 
could fetch the source file and parse the description from it.
I understand that not doing that saves traffic, although I wonder how much.

>> I think it's fixed in Daniel Haxney's package.el fork, though.
>
> If there is a bug, it should be fixed orthogonally to all the rest of
> the refactoring he is trying to do.

I'm sorry for the confusion, his code is not doing anything different in 
that regard. I guess I skimmed it a while ago, saw the related part of 
`describe-package-1', got excited and failed to notice both the 
condition (if built-in) and the fact that that code is the same in the 
Emacs trunk.



  reply	other threads:[~2012-10-27 11:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 16:10 GNU ELPA visibility Dmitry Gutov
2012-10-26 18:31 ` Stefan Monnier
2012-10-26 18:53   ` chad
2012-10-26 19:11     ` Stefan Monnier
2012-10-27  5:18 ` Chong Yidong
2012-10-27 11:26   ` Dmitry Gutov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-02 18:47 Dmitry Gutov
2012-10-28 20:26 Dmitry Gutov
2012-10-28 16:29 Daniel Hackney
2012-10-28 16:47 ` Eli Zaretskii
2012-10-28 18:23   ` Andreas Schwab
2012-10-25 22:14 Dmitry Gutov
2012-10-25 22:47 ` Jorgen Schaefer
2012-10-25 21:23 Dmitry Gutov
2012-10-25 21:34 ` Drew Adams
2012-10-25 21:47   ` Dmitry Gutov
2012-10-25 21:52     ` Drew Adams
2012-10-26  1:37     ` Stefan Monnier
2012-10-25 21:48 ` Jorgen Schaefer
2012-10-25 19:58 Dmitry Gutov
2012-10-25 21:10 ` Stefan Monnier
2012-10-25 19:30 Stefan Monnier
2012-10-25 20:04 ` Jeremiah Dodds
2012-10-25 20:18   ` Drew Adams
2012-10-26  7:29   ` Tassilo Horn
2012-10-27  6:33     ` Bastien
2012-10-26  4:22 ` Jambunathan K
2012-10-27  6:39   ` Bastien
2012-11-01  4:33 ` Stefan Monnier
2012-11-01  5:10   ` Jambunathan K
2012-11-01  5:13     ` chad
2012-11-01  5:18       ` Jambunathan K
2012-11-01 12:42     ` Stefan Monnier
2012-11-02  7:12       ` Daniel Hackney
2012-11-02  7:48         ` Jorgen Schaefer

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=508BC4EC.3060503@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=cyd@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jeremiah.dodds@gmail.com \
    --cc=monnier@IRO.UMontreal.CA \
    /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.