On Mon, 24 Jan 2000, Brian J. Murrell wrote:
[..]
> Yes there is that too. I was going to use that reason too but did not
> want to get accused of being lazy or something for not closely examing
> the "make install" output rather than just looking for the permission
> errors.
not a first for me
> > > The install can be inspected much easier than the build, so doing it
> > as
> > > root is easier to audit and prevent nasties.
> >
> > um uh, didn;t you just contradict your self? or i misread...
>
> I wrote a difficult to understand sentence, sorry. Let me try again:
>
> The rpm install process can be inspected much easier than the "make
> install" process so deferring being root to rpm installation is safer.
>
> > Gotta understand it to patch it out seems doubled work to me..
>
> Sorry Axalon, now it's your turn. I am not sure whether you are
> agreeing or disagreeing with me in that sentence.
To not use the 'make install' specificly the mknod and other such things
you have to patch them out. To patch them out you must deal with the
Makefile's, which means a patch (usualy), which means it will usualy need
updated, which means more knowledge of the Makefile. So you might as well
just do a 'make -n' and save your self the never ending patching cycle.
