Re: GNU ELPA visibility

[Dmitry Gutov <dgutov@yandex.ru>]

Daniel Hackney <dan@haxney.org> writes:

 > Dmitry Gutov wrote:
 >> Tassilo Horn <address@hidden> 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.
 >
 > The problem is with those repos. They don't create a
 > <pkg-name>-readme.txt file. It's particularly strange for Marmalade,
 > since the content which would go into the readme is displayed on the
 > website (though not in <pre> formatting) but isn't available through
 > `list-packages'.

Indeed. And there's been an issue filed on Marmalade's bug tracker for
close to a year now (#36).

I think I will take a stab at fixing this for MELPA.

 >> I think it's fixed in Daniel Haxney's package.el fork, though.
 >
 > Sorry for the confusion (my choice of domain could be clearer), but my
 > last name is "Hackney", not "Haxney". The domain name "haxney.org" is a
 > play on "hacks" => "hax" (sometimes used in videogame-speak) and
 > "Hackney". Also, the username "haxney" is available on every service I
 > have ever come across.

That's my fault, sorry.

 > I was careful not to make any changes to the HTTP and file-based APIs in
 > my branch, so if a repo doesn't provide a readme, then my branch can't
 > do anything about that.

Sorry again, duh.

--Dmitry