On Sun, Oct 14, 2007 at 04:34:20PM -0700, Russ Allbery wrote:
Paul Wise [EMAIL PROTECTED] writes:
Now that dpkg has the Homepage field[1], shall I update the patch to
warn when the homepage is in the description instead of the new field?
Or should we wait for policy and the devref to be
On Thu, 2008-05-01 at 00:43 +0200, Frank Lichtenheld wrote:
I'm still not sure that the original patch in this bug report (trying to
guess at whether a random URL found in the extended description should be
a homepage) is really a good idea.
I personally would vote for closing this bug.
Paul Wise [EMAIL PROTECTED] writes:
Now that dpkg has the Homepage field[1], shall I update the patch to
warn when the homepage is in the description instead of the new field?
Or should we wait for policy and the devref to be updated?
1.
On Sun, 2006-03-26 at 17:14 -0800, Russ Allbery wrote:
I really think the effort would be better spent standardizing an optional
URL field in Policy so that people can start using that, package build
tools can be updated where necessary to handle it, and package viewing and
installation tools
Paul Wise [EMAIL PROTECTED] writes:
On Sun, 2006-03-26 at 17:14 -0800, Russ Allbery wrote:
I really think the effort would be better spent standardizing an
optional URL field in Policy so that people can start using that,
package build tools can be updated where necessary to handle it, and
On Sun, Mar 26, 2006 at 05:14:39PM -0800, Russ Allbery wrote:
Hello folks,
Since I just spent some time looking over the discussion and the patch in
lintian bug #339829 to check for the Homepage information in the
description of packages and decided not to apply it, I figured I should
let
6 matches
Mail list logo
