1 |
Peter Volkov wrote: |
2 |
|
3 |
> Robert Buchholz ?????: |
4 |
>> Thilo Bangert wrote: |
5 |
>> > HOMEPAGE="http://this-package-has-no-homepage.gentoo.org/" |
6 |
>> |
7 |
>> Why not use our package site for this, i.e. |
8 |
>> HOMEPAGE="http://packages.gentoo.org/package/${CAT}/${PN}" |
9 |
> |
10 |
> This is not homepage. HOMEPAGE should point to "package dependent |
11 |
> information" or in other words to upstream. |
12 |
Er it is package-specific, and this is for where there is no upstream. |
13 |
|
14 |
> Same stands to existent or nonexistent link on gentoo.org or any other |
15 |
> domain. This is even worth as this solution also makes users to open |
16 |
> another page which just tell them that homepage does not exist... |
17 |
> |
18 |
No, the packages site links to a forum search (I'd personally make that |
19 |
a 'site:forums.gentoo.org' google search across the board, since it's so |
20 |
much handier, and get some adsense bucks while you're there;) and a |
21 |
bugzilla search, as well as giving information about all the available |
22 |
versions in the tree. You should check it out ;p |
23 |
|
24 |
> So I think if HOMEPAGE does not exist then it's better either put some |
25 |
> constant there or better make it empty. If we wish, for packages with |
26 |
> empty HOMEPAGE we can teach tools like emerge -s or eix to show "Home |
27 |
> page unknown" or "Homepage does not exist". Simple and clear, what else |
28 |
> do we need? :) |
29 |
> |
30 |
An easy way for Gentoo users to contact other people using the software; |
31 |
given that it's available on Gentoo, and officially dead as far as Gentoo |
32 |
is aware, having the cli interface display that url (however formulated) is |
33 |
a plus in support terms, and maybe one day getting the package resurrected. |
34 |
A gui wrapper like himerge would display the link as clickable, as would a |
35 |
suitably configured xterm. |
36 |
|
37 |
So while I agree the empty value in the ebuild is the way to go, I'd |
38 |
personally like it a lot if Portage at least displayed a useful url (and |
39 |
the website was ok with it.) If you're going that far for the official |
40 |
mangler and the site, it seems like something to mandate/specify (I |
41 |
really /don't/ want to file that bug;) |
42 |
|
43 |
Is there at least consensus that the above formulation wrt user-display, and |
44 |
zero-length, would be useful? |
45 |
|
46 |
(Leaving aside concerns over backward-compatibility/EAPI.) |