On Sun, Jan 09, 2000 at 09:38:17PM +, Matthew Vernon wrote:
> OTOH, new packages with lintian errors tend to get rejected - it would
> be unfair to reject new software simply because it contains no man pages...
Frankly, I like the idea. I think packages are being created far too
lightly these
Chris Waters writes:
> Greg Stark <[EMAIL PROTECTED]> writes:
>
> > I think the problem is really that lintian is too picky about lack
> > of man pages. At least, it's impossible to get a package by lintian
> > without setting undocumented links for every binary without a man
> > page, which
Wichert Akkerman <[EMAIL PROTECTED]> writes:
> Policy is a desired state of package, it doesn't dictate a transition
> period.
Right, which is why I've suggested creating a Strategy document or
something similar. It would help avoid this sort of confusion.
--
Chris Waters [EMAIL PROTECTED] |
Greg Stark <[EMAIL PROTECTED]> writes:
> I think the problem is really that lintian is too picky about lack
> of man pages. At least, it's impossible to get a package by lintian
> without setting undocumented links for every binary without a man
> page, which is a sure way to get maintainers to do
Matthew Vernon <[EMAIL PROTECTED]> writes:
> Chris Waters writes:
> > We have a *serious* problem here, IMO, and, while this proposal may
> > not be the best solution, we *need* a solution. I'd like to hear some
> > alternative proposals if this one is to be discarded.
> I'm not sure I agree
> > > I think your ideas may be suitable for wishlist bugs against packages
> > > that don't do what you want, but it shouldn't go into policy.
> >
> > No. The maintainers could close the wishlist without doing anything.
>
> I think that they would only do so if they have a good reason not
Nicolás Lichtmaier writes:
> > I think your ideas may be suitable for wishlist bugs against packages
> > that don't do what you want, but it shouldn't go into policy.
>
> No. The maintainers could close the wishlist without doing anything.
I think that they would only do so if they have a
> > > Web clients should default to try to fetch URLs by a direct connection to
> > > the target host. If the `http_proxy' variable is defined, it should
> > > specify
> > > an URL that would be used as a proxy. Programs should not try to access an
> > > URL directly if this variable is defined. P
> > Web clients should default to try to fetch URLs by a direct connection to
> > the target host. If the `http_proxy' variable is defined, it should specify
> > an URL that would be used as a proxy. Programs should not try to access an
> > URL directly if this variable is defined. Programs that ha
> I propose that "woody" and subsequent releases permit the use of bzip2
> format for source packages.
I second this.
> > This is already standard, but I think it should be into policy because I
> > already saw some programs deviating from this expected behaviour.
> I'm not aware of netscrape doing this, for example. And it's better to
> use /etc/lynx.conf to make lynx do it too, as it prevents lusers
> forgetti
Julian Gilbey <[EMAIL PROTECTED]> writes:
> On Sun, Jan 09, 2000 at 12:50:29AM -0300, Nicolas Lichtmaier wrote:
> > Package: debian-policy
> >
> > This is already standard, but I think it should be into policy because I
> > already saw some programs deviating from this expected behaviour.
> >
>
Matthew Vernon <[EMAIL PROTECTED]> writes:
> I still maintain that undocumented(7) serves a useful function (as my
> objection said), but perhaps it should be reworded somewhat; maybe we
> should encourage people to check the BTS and submit a bug report, or
> simply "do submit this as a bug if th
I second the proposal.
On Sun, Jan 09, 2000 at 10:35:16 +, Julian Gilbey wrote:
> Are these environment variables,
Yes.
It would be nice if more programs supported them (I'm thinking of nsgmls in
particular - at work, http connections to the outside only work through the
proxy, and I've foun
On Wed, 05 Jan 2000, Chris Waters wrote:
> > So you are saying that packers are omitting an EXISTING manpage,
> > and instead putting a link to the undocumented.7 page?
> No, what he's saying is that people *routinely* use undocumented(7)
> *without* any bug report on file.
That's exactly the po
Chris Lawrence <[EMAIL PROTECTED]> writes:
> Package: debian-policy
> Version: 3.1.1.1
> Severity: wishlist
>
> I propose that "woody" and subsequent releases permit the use of bzip2
> format for source packages. [...]
I second this proposal.
Falk
On Sun, Jan 09, 2000 at 12:50:29AM -0300, Nicolás Lichtmaier wrote:
> Package: debian-policy
>
> This is already standard, but I think it should be into policy because I
> already saw some programs deviating from this expected behaviour.
>
> Web clients should default to try to fetch URLs by a di
Chris Waters writes:
> We have a *serious* problem here, IMO, and, while this proposal may
> not be the best solution, we *need* a solution. I'd like to hear some
> alternative proposals if this one is to be discarded.
> (cc'd to the most recent objectors in the probably vain hope that
> th
> This is already standard, but I think it should be into policy because I
> already saw some programs deviating from this expected behaviour.
I'm not aware of netscrape doing this, for example. And it's better to
use /etc/lynx.conf to make lynx do it too, as it prevents lusers
forgetting to co
> > This is already standard, but I think it should be into policy because I
> > already saw some programs deviating from this expected behaviour.
> >
> > Web clients should default to try to fetch URLs by a direct connection to
> > the target host. If the `http_proxy' variable is defined, it shou
On Sun, Jan 09, 2000 at 12:50:29AM -0300, Nicolás Lichtmaier wrote:
> Package: debian-policy
>
> This is already standard, but I think it should be into policy because I
> already saw some programs deviating from this expected behaviour.
>
> Web clients should default to try to fetch URLs by a di
On Jan 09, Nicolás Lichtmaier wrote:
> Package: debian-policy
>
> This is already standard, but I think it should be into policy because I
> already saw some programs deviating from this expected behaviour.
Time for some wishlist bugs, then, I guess...
> Web clients should default to try to fetc
Previously Anand Kumria wrote:
> That is not what policy 6.4 says.
Policy is a desired state of package, it doesn't dictate a transition
period. In this case the technical committee did give us a detailed
transition process.
Wichert.
--
___
Package: debian-policy
This is already standard, but I think it should be into policy because I
already saw some programs deviating from this expected behaviour.
Web clients should default to try to fetch URLs by a direct connection to
the target host. If the `http_proxy' variable is defined, it
On Jan 09, Anand Kumria wrote:
> Here is an additional question: what standards release(s) will be
> allowed in potato?
My understanding is that >= 2.5.0.0 is acceptable for potato. But I
don't think that's official or set in stone.
On the /usr/share/doc thing... if the maintainer has made subst
On Sun, 9 Jan 2000, Roland Rosenfeld wrote:
> On Sun, 09 Jan 2000, Anand Kumria wrote:
>
> > > Who is expecting 0 here? We expect this for Debian 2.3, but not
> > > for potato. In potato we expect, that every documentation is
> > > available as /usr/doc/ (documentation either placed there
> > >
On Sun, 09 Jan 2000, Anand Kumria wrote:
> > Who is expecting 0 here? We expect this for Debian 2.3, but not
> > for potato. In potato we expect, that every documentation is
> > available as /usr/doc/ (documentation either placed there
> > or accessible via a symlink to /usr/share/doc/).
> No,
27 matches
Mail list logo
