[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU ELPA visibility

From: Dmitry Gutov
Subject: Re: GNU ELPA visibility
Date: Mon, 29 Oct 2012 00:26:50 +0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1

Daniel Hackney <address@hidden> 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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]