Hiya.
Boaz Rymland wrote:
>
> Hi,
>
> Regarding managing software: Using rpm (and it's graphical
> implementations) is very easy and comfortable, but I prefer compiling
> everything I can for performance (and stability?) reasons.
> First, does it "pay-off" to do that? I mean compiling even small app.
> to KDE. Is performance really improving.?
Size, performence, etc. Depends.
> Second, I guess that compiling the basic KDE bundles is good, but is
> there a way to avoid using "--nodeps" on every small KDE package I
> would like to install ever since? (cause KDE isn't registered in rpm
> database).
Just use SRPMs. You can either just rebuild the binary rpm and
install it (--rebuild) without making any configuration changes,
or you can install it, edit the spec file (possibly creating
a patch, just changing the Makefile, etc) and -bb'ing (*cough*)
the spec file. There, you still have your precious rpm db :)
> Third, is there a managing tool for software compiled and installed "by
> hand" ? (for querying and info.)
>
> Thank's
Several install wrappers exist (some syscall wrappers,
other just scan everything). Never tried one, search
freshmeat.
--
Omer Efraim
!- Software: Making your computer come alive so it can attack you -!
Dave Barry in Cyberspace (probably using Windows)
