Hello Margarita and *,
Am 2006-12-14 15:11:48, schrieb Margarita Manterola:
> I'm planning on preparing a patch for dpkg to add the Homepage field
> to the control fields of the package. Will most probably work on this
> during the summer [1]. Maybe then we can stop the stupid "one space"
> vs "
On 12/14/06, Russ Allbery <[EMAIL PROTECTED]> wrote:
> Does the Lintian issua an information message of any kinf for the
> Homepage: field? If it would, the maintainers could possibly pay more
> attention. Not many are aware of the spcae or "two space" reason for
> long URLs.
No. There's a prop
Jari Aalto <[EMAIL PROTECTED]> writes:
> Does the Lintian issua an information message of any kinf for the
> Homepage: field? If it would, the maintainers could possibly pay more
> attention. Not many are aware of the spcae or "two space" reason for
> long URLs.
No. There's a proposed patch that
Russ Allbery <[EMAIL PROTECTED]> writes:
> Margarita Manterola <[EMAIL PROTECTED]> writes:
>
> > When the URL is something like http://www.myniceproject.org, I don't see
> > that would be the difference in having the extra space or not.
>
> Well, it matters to people with 20-character-wide windo
On Thu, 2006-06-15 at 11:13 +0200, Vincent Danjean wrote:
> It is the case (20-character-wide windows or less) with some terminals
> for blind people... In this case, one more character increase the cost
> of the terminal, so there are not many.
If the terminal is not more wide than 20 characters
Russ Allbery wrote:
> Margarita Manterola <[EMAIL PROTECTED]> writes:
>
>> When the URL is something like http://www.myniceproject.org, I don't see
>> that would be the difference in having the extra space or not.
>
> Well, it matters to people with 20-character-wide windows, if there are
> any s
There's two points to this discussion:
1) The original issue I touched, which is whether the extended advice on
a space in front of the Homepage 'field' is necessary;
2) A spin-off discussion: do we need a homepage field at all or do
we need to provide it in another way.
As to the first poin
On 6/15/06, Don Armstrong <[EMAIL PROTECTED]> wrote:
> That is a point, but still the users might find the link useful.
> Also, checking if something fresher is present is in upstream could
> be facilitated because there is no need to look for the copyright
> file and ge the info from there.
Thi
Adam Borowski <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 15, 2006 at 12:11:32AM +0800, Paul Wise wrote:
>> I don't think any part of packages (description or separate field) are
>> the correct place for the Homepage field.
>
> Yes, that's because it's an unneeded duplication of what's already
> pres
Adam Borowski <[EMAIL PROTECTED]> writes:
> Yes, that's because it's an unneeded duplication of what's already
> present in /usr/share/doc/*/copyright. The description is meant to
> convey information about where you can find useful things about the
> package, not about where you can download a n
On Thu, 15 Jun 2006, Eddy Petrişor wrote:
> On 6/15/06, Don Armstrong <[EMAIL PROTECTED]> wrote:
> >if someone wanting to NMU is incapable of examining the copyright
> >file to find the location of upstream, they shouldn't be making an
> >NMU.
>
> That is a point, but still the users might find th
On 6/15/06, Don Armstrong <[EMAIL PROTECTED]> wrote:
On Thu, 15 Jun 2006, Eddy Petrişor wrote:
> Think about somebody wanting to NMU because a bug has a fix in
> upstream and the current mainatiner is too busy or MIA. How
> difficult is it to get to the upstream? Is REALLY hard, belive me!
I hat
On Thu, 15 Jun 2006, Eddy Petrişor wrote:
> Think about somebody wanting to NMU because a bug has a fix in
> upstream and the current mainatiner is too busy or MIA. How
> difficult is it to get to the upstream? Is REALLY hard, belive me!
I hate to point this out this pointedly, but if someone want
On Thu, Jun 15, 2006 at 01:41:06AM +0300, Eddy Petri??or wrote:
> >> I don't think any part of packages (description or separate field) are
> >> the correct place for the Homepage field.
> >
> >Yes, that's because it's an unneeded duplication of what's already
> >present in /usr/share/doc/*/copyrig
On 6/15/06, Goswin von Brederlow
<[EMAIL PROTECTED]> > > Policy does not talk about
URLs, it just explains what the extra space is for.
It matters if you have
http://www.my.real.long.and.cool.domain.name.that.i.so.love.net/all/my/projects/package/html/
C'mon, how often does that happen? 1 in
On 6/15/06, Adam Borowski <[EMAIL PROTECTED]> wrote:
On Thu, Jun 15, 2006 at 12:11:32AM +0800, Paul Wise wrote:
> I don't think any part of packages (description or separate field) are
> the correct place for the Homepage field.
Yes, that's because it's an unneeded duplication of what's already
"Margarita Manterola" <[EMAIL PROTECTED]> writes:
> On 6/14/06, Russ Allbery <[EMAIL PROTECTED]> wrote:
>
>> The space is necessary; it tells package front-ends to not wrap the line.
>> See Policy 5.6.13.
>
> I guess you are referring to:
>
> "Those starting with two or more spaces. These will be
On Thu, Jun 15, 2006 at 12:11:32AM +0800, Paul Wise wrote:
> I don't think any part of packages (description or separate field) are
> the correct place for the Homepage field.
Yes, that's because it's an unneeded duplication of what's already
present in /usr/share/doc/*/copyright. The description
On Wed, 2006-06-14 at 08:27 -0700, Russ Allbery wrote:
> Thus proving that the real solution is to get rid of the Homepage bit
> completely and instead add a real field to dpkg, since people won't even
> agree on and follow the syntax for the hack of putting it in the long
> description so that pe
Margarita Manterola <[EMAIL PROTECTED]> writes:
> When the URL is something like http://www.myniceproject.org, I don't see
> that would be the difference in having the extra space or not.
Well, it matters to people with 20-character-wide windows, if there are
any such people (there could potentia
On 6/14/06, Russ Allbery <[EMAIL PROTECTED]> wrote:
The space is necessary; it tells package front-ends to not wrap the line.
See Policy 5.6.13.
I guess you are referring to:
"Those starting with two or more spaces. These will be displayed
verbatim. If the display cannot be panned horizontall
On Wed, Jun 14, 2006 at 01:35:57PM +0200, Thijs Kinkhorst wrote:
> On Fri, 2006-05-19 at 14:25 +0200, Thijs Kinkhorst wrote:
> > On Fri, 2006-05-19 at 13:09 +0100, Adam James wrote:
> > > A minor quibble with your post, the following is from the Debian
> > > Developer's Reference [0]:
> > >
> > >
Thijs Kinkhorst <[EMAIL PROTECTED]> writes:
> On Fri, 2006-05-19 at 14:25 +0200, Thijs Kinkhorst wrote:
>> Hmm indeed, but to be honest I don't understand dit. I can't tell how
>> this extra space will aid in the breaking of lines? The only space in
>> that line will be right after "Homepage:" and
On Fri, 2006-05-19 at 14:25 +0200, Thijs Kinkhorst wrote:
> On Fri, 2006-05-19 at 13:09 +0100, Adam James wrote:
> > A minor quibble with your post, the following is from the Debian
> > Developer's Reference [0]:
> >
> > Note the spaces prepending the line, which serves to break the lines
> > corr
24 matches
Mail list logo
