>>"Christian" == Christian Hammers <[EMAIL PROTECTED]> writes:
Christian> ... to be replaced by what? The maintainers simply won't
Christian> write manpages en mass, so when deleting undocumented(1)
Christian> many packages will have binaries without manpage making it
Christian> harder for new
> > > has been useless more often than I liked... thanks to undocumented(1).
On Mon, 28.08.00 13:03 -0400, Raul Miller wrote:
> > Wasn't there a policy proposal to get rid of these bogus pages?
On Fri, Aug 25, 2000 at 07:50:29PM +0200, Christian Hammers wrote:
> ... to be replaced by what? The ma
Hello
On Mon, 28.08.00 13:03 -0400, Raul Miller wrote:
> > has been useless more often than I liked... thanks to undocumented(1).
> Wasn't there a policy proposal to get rid of these bogus pages?
... to be replaced by what? The maintainers simply won't write manpages
en mass, so when deleting undo
On Mon, Aug 28, 2000 at 06:36:16PM +0200, "J?rgen A. Erhard" wrote:
> "dpkg -L foo |grep man"
>
> has been useless more often than I liked... thanks to undocumented(1).
Yep, another reason for getting rid of that junk.
[Personally, I've got dpkg redirected so that the cover
script fires up a li
"dpkg -L foo |grep man"
has been useless more often than I liked... thanks to undocumented(1).
Just my EU 0.02
Bye, J
--
Jürgen A. Erhard[EMAIL PROTECTED] phone: (GERMANY) 0721 27326
My WebHome: http://members.tripod.com/Juergen_Erhard
Debian GNU/Linux (http://w
On 23-Aug-00, 18:17 (CDT), Daniel Barclay <[EMAIL PROTECTED]> wrote:
> > From: Steve Greenland <[EMAIL PROTECTED]>
> > ... Current policy
> > requires that /usr/doc/ exist (possibly as a symlink to
> > /usr/share/doc/).
>
> Then why don't more package implement that policy?
Because they're *brok
On Wed, Aug 23, 2000 at 07:17:32PM -0400, Daniel Barclay wrote:
> > From: Steve Greenland <[EMAIL PROTECTED]>
> > ... Current policy
> > requires that /usr/doc/ exist (possibly as a symlink to
> > /usr/share/doc/).
> Then why don't more package implement that policy?
If the package doesn't do th
There are probably 2 packaging interfaces you could check out ..
kpackage (not part of debian i dont think but available from
kde.tdyc.com)
gnome-apt
nate
Anthony Towns wrote:
>
> On Wed, Aug 23, 2000 at 07:17:32PM -0400, Daniel Barclay wrote:
> > > > Debian packages don't provide that orientat
From: Steve Greenland <[EMAIL PROTECTED]>
> > ... Current policy
> > requires that /usr/doc/ exist (possibly as a symlink to
> > /usr/share/doc/).
On Wed, Aug 23, 2000 at 07:17:32PM -0400, Daniel Barclay wrote:
> Then why don't more package implement that policy?
Please give some examples of pac
On Wed, Aug 23, 2000 at 07:17:32PM -0400, Daniel Barclay wrote:
>
>
> So? I didn't say it was. I didn't say that Debian maintainers
> should clean up upstream documentation.
>
> I just argued that in doc directory, which typically contains
> a mess of upstream files, there should be a file tha
On Wed, Aug 23, 2000 at 07:17:32PM -0400, Daniel Barclay wrote:
> > > Debian packages don't provide that orientation reliably at all.
> > ls -l /usr/doc/foo
> > dpkg -L foo |grep bin
> > dpkg -L foo |grep man
> > dpkg -L foo |grep info
> > works for *every* package. (Yes, I know it would be more e
> From: Steve Greenland <[EMAIL PROTECTED]>
>
> On 22-Aug-00, 23:12 (CDT), Daniel Barclay <[EMAIL PROTECTED]> wrote:
> > ...
>
> ... Current policy
> requires that /usr/doc/ exist (possibly as a symlink to
> /usr/share/doc/).
Then why don't more package implement that policy?
> > Some othe
>>"Daniel" == Daniel Barclay <[EMAIL PROTECTED]> writes:
Daniel> Some packages don't have a documentation directory at all.
Umm. Packages are _required_ to have a /usr/doc/
symlink/directory. Can you please point to the packages that do not,
so we can file important bugs against them?
On 22-Aug-00, 23:12 (CDT), Daniel Barclay <[EMAIL PROTECTED]> wrote:
> Some packages don't have a documentation directory at all.
Then they are in violation of the Debian policy. Current policy
requires that /usr/doc/ exist (possibly as a symlink to
/usr/share/doc/).
> Some others do but their f
On Wed, Aug 23, 2000 at 12:12:47AM -0400, Daniel Barclay wrote:
> Why? Because of all the times I've needed such information and it
> wasn't there or was hard to find.
What's insufficient about dpkg -L ? (Or, if you've forgotten
why you wanted to install the package, dpkg -s to look at the
descr
> From: Rogerio Brito <[EMAIL PROTECTED]>
> On Aug 19 2000, John Ackermann wrote:
> > I heartily agree with Daniel's plea. Eveb a simple listing of what
> > configuration files the package uses (and where they are), and where it
> > stores data (i.e., does it use space in /var) would be a bi
debian-user trimmed.
On Sat, Aug 19, 2000 at 10:31:14PM +0200, Marco d'Itri wrote:
> On Aug 19, John Ackermann <[EMAIL PROTECTED]> wrote:
> >I heartily agree with Daniel's plea. Eveb a simple listing of what
> >configuration files the package uses (and where they are), and where it
> >stores
On Sat, Aug 19, 2000 at 12:55:25PM -0700, Chris Waters wrote:
> silly. I venture to guess that 80% of all packages have a binary that
> matches the package name, and don't need *any* (re)configuration. And
> of the remainder, most do have adequate documentation already.
I haven't checked recentl
> >I heartily agree with Daniel's plea. Eveb a simple listing of what
> >configuration files the package uses (and where they are), and where it
> >stores data (i.e., does it use space in /var) would be a big help.
> less /var/lib/dpkg/info/.list
>
> If you really care, write a nice wrapper
On Aug 19, John Ackermann <[EMAIL PROTECTED]> wrote:
>I heartily agree with Daniel's plea. Eveb a simple listing of what
>configuration files the package uses (and where they are), and where it
>stores data (i.e., does it use space in /var) would be a big help.
less /var/lib/dpkg/info/.list
>
> Why don't all Debian packages come with installation instructions
> in a _standard_ place that tell you what you need to do (after
> installing the package) to configure or use the package you just
> loaded?
I heartily agree with Daniel's plea. Eveb a simple listing of what
configuration
On Sat, Aug 19, 2000 at 03:23:22PM -0400, Daniel Barclay wrote:
> Why don't all Debian packages come with installation instructions
> in a _standard_ place that tell you what you need to do (after
> installing the package) to configure or use the package you just
> loaded?
Most Debian packages
Why don't all Debian packages come with installation instructions
in a _standard_ place that tell you what you need to do (after
installing the package) to configure or use the package you just
loaded?
There needs to be a standard place to consult to know what a
package needs (setup) and what i
23 matches
Mail list logo
