Re: sudo make install

[Martin <martin@marcher.name>]

This might be controversial :)

I've never been a fan of requiring root (uid 0) rights to install software
in site-specific plases -- or install any software for that matter, but
that topic is for a different mailing list. :)

So this is what I've been doing for quite some time:

* Use some "swadm" (Software Administration) group that has R/W access to
the relevant directories (presumably /usr/local in your case)
** Maybe even extend that to "swadm-emacs" (or any other package)

I only have to deal with the major distributions so /usr/local is enough
for me. With the *BSD stuff you might want to choose a different site
prefix, AFAIR ports/packages installs in /usr/local.

Make yourself a member of that group and be done with it.

In my specific case:

I do like to build _and_ install with the same account. Yes that may be
risky in case a build or install step goes south but practically I found
that to be the easiest choice.

regards,
Martin

On Wed, Apr 15, 2015 at 3:10 AM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:

> > My question: when I want to "make install", I need to use "sudo".  But
> > after that operation, the emacs/ source dir now contains files owned by
> > root.
>
> A "make install" right after "make" should not create/touch local files
> (exactly for the reason you show).  So if you do get some root-owned
> files even though you did a (non-root) "make" right before the "make
> install", I recommend you M-x report-emacs-bug.
>
>
>         Stefan
>
>
>