On Thu, 24 Aug 2000 12:49:42 +1000, Anand Kumria
<[EMAIL PROTECTED]> wrote:
>README.Debian exists in the package(s) which have made substainial changes
>to how the package operates. If it exists it contains important information
>that the maintainer wanted you to read.
However, Debian's apache com
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
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
bish wrote:
> Just to find out what all packages are installed, there are no easy
> solutions.
dpkg -l
--
see shy jo
On Sun, Aug 20, 2000 at 09:34:54AM -0500, John Hasler wrote:
> Bish writes:
> > There is a need for something like gnorpm/ kpackage/ glint used
> > in RH and other RH based distros.
>
> Have you looked at console-apt?
Not to mention aptitude, gnome-apt, and good old dselect (hey, i like
it). apt
On Sun, Aug 20, 2000 at 05:33:05PM +0530, bish wrote:
> If there is anything called "users-requests" this certainly should be
> placed there for the kind Debian developers to take notice. Surely,
the best way to make a feature request is probably to file a
*wishlist* bug against package `general'
Frankly NO. It is not there in my CD based distribution from where I
installed. It must be a later on addition to the debian applications after
release of slink. I'll do an apt-get for this and give a try. Thanks.
Just one last question. Does it work on local file systems as well, when
the connect
Bish writes:
> There is a need for something like gnorpm/ kpackage/ glint used
> in RH and other RH based distros.
Have you looked at console-apt?
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
If there is anything called "users-requests" this certainly should be
placed there for the kind Debian developers to take notice. Surely,
dpkg --search / list / listfiles / print-avail is no replacement for a
dedicated package/ wrapper for these purposes.
Just to find out what all packages are in
André writes:
> If you're only interested in which config files a certain program uses
> you can do something like:
> dpkg -s package_name
> and read the part after "Conffiles:".
Yes, of course I can: I'm a Debian developer and I have been using Debian
since 1.1. The average new user, however,
On Sat, Aug 19, 2000 at 07:50:31PM -0500, John Hasler wrote:
> That produces a list that is certain to be incomprehensible to a new user.
If you're only interested in which config files a certain program uses
you can do something like:
dpkg -s package_name
and read the part after "Conffiles:".
Shaul Karl writes:
> Are not the contents of /usr/share/doc/package contain this info?
No. It usually just contains the Debian changelog, the copyright files,
and any miscellaneous docs from upstream (often none).
> Isn't
> dpkg -L package
> yield the list of files that are installed by
> >
> > 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?
>
Are not the contents of /usr/share/doc/package contain this info?
>
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 big help.
All packages *do* already have such f
> >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
26 matches
Mail list logo
