(I fondly remember my second slackware install. I had found out enough the
first time around to know that the names of commands was key to learning
linux. Several of the core slackware packages listed all the commands in
them in their descriptions, and raced against the install to get the command
n
Joey Hess <[EMAIL PROTECTED]> writes:
> Chris Waters wrote:
> > I think people are becoming too ready to propose grand, sweeping
> > changes to policy in order to fix obscure, minor problems.
> I agree.
> > If you *really* want something in policy, I'd suggest: "the package
> > description shoul
Chris Waters wrote:
> I think people are becoming too ready to propose grand, sweeping
> changes to policy in order to fix obscure, minor problems.
I agree.
> If you *really* want something in policy, I'd suggest: "the package
> description should list the binaries (or at least, the main binary)
Goswin Brederlow schrieb am Dienstag, den 23. November 1999:
> Policy says that any binary must come with a manpage. I would like
> to have the same for packages.
I'm not sure, whether such a general rule is acceptable. Think for
example about the long list of libstdc++* packages: Should we wri
Goswin Brederlow <[EMAIL PROTECTED]> writes:
> Policy says that any binary must come with a manpage. I would like to have
> the same for packages.
I think I disagree. What section would be appropriate?
I think people are becoming too ready to propose grand, sweeping
changes to policy in order t
Previously Ben Collins wrote:
> How about someone write a script that pulls all of the packages and if
> there isn't a man page matching the package name, create one using the
> package's description as the content. Call it "update-packageman" or
> something.
shellutils contains a funky script tha
On Tue, Nov 23, 1999 at 07:31:01PM +0100, Goswin Brederlow wrote:
> Package: debian-policy
> Version: 3.1.1.0
> Severity: wishlist
>
> Policy says that any binary must come with a manpage. I would like to have
> the same for packages.
>
> I just looked for a parser generator that outputs C++ code
perhaps it would be a nice extension to list all the config files owned by
that package...
On Tue, Nov 23, 1999 at 07:31:01PM +0100, Goswin Brederlow wrote:
> Package: debian-policy
> Version: 3.1.1.0
> Severity: wishlist
>
> Policy says that any binary must come with a manpage. I would like t
Package: debian-policy
Version: 3.1.1.0
Severity: wishlist
Policy says that any binary must come with a manpage. I would like to have
the same for packages.
I just looked for a parser generator that outputs C++ code and found pccts.
After installation I tried "man pccts", but that failed.
/usr/do
9 matches
Mail list logo
