Linux Newbie help
 help / color / mirror / Atom feed
From: whitnl73@juno.com
To: ray@comarre.com
Cc: linux-newbie@vger.kernel.org
Subject: Re: distribution choice
Date: Fri, 28 Feb 2003 01:17:05 -0500 (EST)	[thread overview]
Message-ID: <20030228.012503.8.0.whitnl73@juno.com> (raw)
In-Reply-To: <5.1.0.14.1.20030227152314.01f2e110@celine>

On Thu, 27 Feb 2003, Ray Olszewski wrote:

> Probably about as informative as RPMs are. That is to say, good but not
> great. Package names usually make sense, and searchig the package cache
> usually finds what you want. But sometimes your search terms are too vague
> to work ... you recall recently a question here about "rec", for example.
> Trying to search the package archive for "rec" matched 100+ packages ... a
> hopeless screening task. The real lack I find is my inability to query the
> database about what package contains a particular file ... there is a way
> to do this if the package is installed on the host, but not if you want the
> app and need to find out which package contains it. (In this respect, I was
> spoiled by Slackware, which always included a complete list, easily
> grep'able, of the complete contents of of every package.)
>
rpm keeps a database of rpm's it has installed, which can be queried by
rpm -qf <filename>
right, I guess you said the debian package manager has an equivalent;
you can make a database of all packages with something like

rpm -qlip /where/the/rpms/are/* >rpmlist

although this is not exactly grep'able, you are better off using
 less -ni
on it, so you can scan for the filename and then back up to the -i entry
for that package which has the package name.  I guess if somebody really
cares I could come up with a way to make a grep'able rpmlist.  I bet you
could do the same with the debian package manager.

You don't _have_ to use any distro, and you can drop packages from one
distro on top of another distro, as long as you are willing to keep
track of the dependencies yourself.  that is what
rpm --nodeps <package file name>
is for, FI.

Of course, if you get the source and compile/install the package
yourself, it isn't known to any package manager...

If you want to use Wine, you do better to get the source, uninstall any
packages of it you may have, and build it yourself.  Distros that carry
it put it in different places, and you may get version problems I don't
want to debug again otherwise.

Lawson
---oops---








________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

      parent reply	other threads:[~2003-02-28  6:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 18:59 distribution choice Haines Brown
2003-02-27 19:12 ` pa3gcu
2003-02-27 19:24 ` Brian Jackson
2003-02-27 22:19   ` Haines Brown
2003-02-27 20:02 ` Ray Olszewski
2003-02-27 23:07   ` Haines Brown
2003-02-27 23:49     ` Ray Olszewski
2003-02-28  1:25       ` james niland
2003-02-28 13:30         ` Frank Roberts
2003-02-28 15:38           ` Ray Olszewski
2003-02-28  6:17       ` whitnl73 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030228.012503.8.0.whitnl73@juno.com \
    --to=whitnl73@juno.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox