> On Mon, 28 Aug 2000, Nitebirdz wrote:
>
> >Date: Mon, 28 Aug 2000 13:51:17 -0500 (CDT)
> >From: Nitebirdz <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Content-Type: TEXT/PLAIN; charset=US-ASCII
> >Subject: Re: rawhide: kudzu-0.68-1 fails to compile
> >
> >On Sun, 27 Aug 2000, John Summerfield wrote:
> >
> >>
> >> I've chowned it to me and do not build as root (regulars will have noticed
> I'm
> >> reluctant to build anything as root; recent news wrt pinstrip is Good).
> >>
> >
> >Excuse me for the stupid question, but why wouldn't you build a package as
> >root? Security reasons? Even if you trust the sources? Just trying to
> >learn something from you, guys. :-)
>
> Because I have done so for several years with no problems until
> last week when I had a "rpm --rebuild" delete several
> subdirectories on my filesystem during "%clean" stage. RPM
Ha ha;-) You had a backup, of course?
I'd not thought of that one. I've a throwaway system here (it's new box, and I
plan to put 7.0 on it before commissioning it; in the mantime it's getting
some exercise while I figure what I want on it), and I HAVE been building as
root on that box.
In my case, it was exclusive (I think!) rpms I'd already built as non-root.
I could well have done the same thing...
> should IMHO do anything it does in a chroot()'d jail. Making a
And just what would you want in that gaol?
For starters, read the rpm config files and see what utilities it uses
internally. Add your compilers, bison, flex, m4, perl, `rpm -qa | egrep
.-devel-`
> user called "rpm" and setting up rpm to build packages as that
> user, is much safer, ESPECIALLY when constructing and debugging
> your own packages.
Configure buildroot and a few other things in ~/.rpmmacros
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
