From: Hans de Graaff <graaff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Projects without a homepage, and valid contents of HOMEPAGE (per bug 239268)
Date: Mon, 06 Oct 2008 08:49:04 +0200 [thread overview]
Message-ID: <1223275745.25947.2.camel@ip6-localhost> (raw)
In-Reply-To: <48E9B257.7070309@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
On Sun, 2008-10-05 at 23:38 -0700, Josh Saddler wrote:
> Ulrich Mueller wrote:
> >>>>>> On Sun, 5 Oct 2008, Robin H Johnson wrote:
> >
> >>>> HOMEPAGE="http://this-package-has-no-homepage.gentoo.org/"
> >>> That would impose needless lookups on subdomains of gentoo.org for
> >>> clients trying to load the homepage.
> >> http://gentoo.org/package-has-no-homepage/ then.
> >
> > Couldn't a page be created at this URL, with a notice that the package
> > has no real homepage?
>
> I think that'd take too much time to create and maintain that sort of
> thing, especially once old packages are finally removed from the tree.
I think the suggestion is to have one generic homepage for all packages
without one, not a Gentoo-specific homepage for each project.
> Why not just stick in a message that says "This package has no
> homepage"? Or "none"? Is there any reason why that couldn't go into the
> HOMEPAGE="" variable? Will it break QA tools and other utilities?
I guess there are a bunch of tools out there that expect a URL in
HOMEPAGE, so providing one will not raise any potential
incompatibilities.
Hans
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-06 6:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 10:44 [gentoo-dev] Projects without a homepage, and valid contents of HOMEPAGE (per bug 239268) Robin H. Johnson
2008-10-05 11:56 ` Dawid Węgliński
2008-10-05 17:45 ` [gentoo-dev] " Ryan Hill
2008-10-05 20:20 ` Philip Webb
2008-10-05 20:23 ` [gentoo-dev] " Ciaran McCreesh
2008-10-05 21:55 ` Thilo Bangert
2008-10-06 2:52 ` Alec Warner
2008-10-06 2:52 ` Robin H. Johnson
2008-10-06 6:19 ` Ulrich Mueller
2008-10-06 6:38 ` Josh Saddler
2008-10-06 6:49 ` Hans de Graaff [this message]
2008-10-06 7:47 ` Jeroen Roovers
2008-10-06 17:22 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-10-06 18:46 ` Jeroen Roovers
2008-10-06 6:02 ` Duncan
2008-10-06 13:59 ` [gentoo-dev] " Robert Buchholz
2008-10-07 11:46 ` [gentoo-dev] " Steve Long
2008-10-08 9:26 ` Brian Harring
2008-10-08 19:23 ` [gentoo-dev] " Steve Long
2008-10-11 9:32 ` [gentoo-dev] " Peter Volkov
2008-10-13 2:00 ` [gentoo-dev] " Steve Long
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=1223275745.25947.2.camel@ip6-localhost \
--to=graaff@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox