Mailinglist Archive: opensuse (2488 mails)

["Rami Michael" <thikrat@xxxxxxxxx>]

Hello All,

I have been using Linux for a long time now but up until recently I
never really did a lot of "configure make install" type builds for any
of my boxes.  As luck had it, there was an rpm available 99% of the
time.

Recently, I have run into a lot of scenarios where I needed a newer
version of something and I had to go through a manual build process.
Currently,  have 3 systems that are pretty much identical.  So lets
say I want a newer version of wireshark or a gnome-applet that suse
does not have yet in a repo.

I would do the standard config make install procedure on all three
boxes.  I did notice that if the linux systems seem to be the same
(ie. x86, i386) I can copy compiled binaries over to another box and I
can use them there.

Here is where my questions begin :)

#1.  Most of these apps have a lot of requirements when you build
them, for example libpcap-devel or gnome-something-devel.  I realized
I do not need the "*devel*" rpms to be installed on the boxes i was
compiling to.  However, since there is no dependancy checking when I
copy something over how can I know that the libpcap libraries actually
exist?  I assume my app will bomb out in the middle?

#2.  If I compile something on 586 openSuse will it work in 586 CentOS
?  Is this just not a smart thing to do?  Should you only copy between
the same distro?

#3.  is there any way to keep track of the files installed?  Or am I
doing something findamentally wrong?  Do I ./configure and make on one
system and then do a make install on all of them?

#4.  How does one easily uninstall stuff that is installed by these methods?

Thanks for any help
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx