Mixing Self Compiled and RPM Packages

I wanted to install some rpm files (latest ntfsprogs). They had some
dependencies that could not be met with other rpms so I downloaded and
compiled the dependencies myself (latest libfuse).

I was again told that the dependencies still did not exist even though
they did. I assume rpm checks against an rpm database rather than the
computer's hard disk for dependencies? I installed the rpms with
--nodeps and it all (kind of) works.

Is there a better way of doing this? E.g should I build an rpm after the
make has finished compiling then install my new rpm? Is there an easy
way (i.e. automated) way of building said rpm or will I need to do quite
a bit of work?

Thanks in advance,

Tim.

Tim Milstead <tim_milstead.RemoveThis@yahoo.co.uk> wrote:
> I wanted to install some rpm files (latest ntfsprogs). They had some
> dependencies that could not be met with other rpms so I downloaded and
> compiled the dependencies myself (latest libfuse).
>
> I was again told that the dependencies still did not exist even though
> they did. I assume rpm checks against an rpm database rather than the
> computer's hard disk for dependencies?

That is indeed the case (although various dependencies are generated
automatically). If you know what you doing and why you can write
yourself a small rpm which does nothing but "Provides:" some things
you are missing. Not that this is generally recommended.

> I installed the rpms with --nodeps and it all (kind of) works.
>
> Is there a better way of doing this?

Well, yes. On the long-term maitenance it is not a very good idea to
mix-and-match some rpms and some things which you are just dropping into
the system - with possible exceptions when what you have packaged does
NOT depend on these other pieces. The later case is still not clear cut
as you may be _updating_ those things long time after you forgot where
and why all pieces went.

Binaries you "downloaded and compiled" most likely already were packaged
as rpms, because your new stuff had dependencies on those, and even if
binaries do not fit recompiling source rpms is not harder then doing
that otherwise. Often 'rpmbuild --rebuild some-package.src.rpm' is good
enough. Even if you cannot find anyting writing a spec file for your
sources is in most cases rather simple thing. With 'rpm-mode' present
emacs will even write a skeleton spec file for you and you have to just
fill in a few things. Yes, this is more work than just "untar,
configure, make" but on the long run it actually saves much more than an
initial investment.

The same applies if you are using some other packaging system, like
dpkg - for example.

Saying all of that you may still want to have a look at
http://asic-linux.com.mx/~izto/checkinstall/
It is not a perfect solution, and does not seem to work with an
absolute reliabiilty, but it still may tide you over if you want
something quick (and not so clean).

Michal