From: Francis Galiegue <fge@one2team•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: "Matthias Andree" <matthias.andree@gmx•de>, git@vger•kernel.org
Subject: Re: [PATCH v3] To make GIT-VERSION-FILE, search for git more widely
Date: Sat, 9 May 2009 19:10:46 +0200 [thread overview]
Message-ID: <200905091910.46775.fge@one2team.com> (raw)
In-Reply-To: <7vskje6wsy.fsf@alter.siamese.dyndns.org>
Le Saturday 09 May 2009 18:55:09 Junio C Hamano, vous avez écrit :
[...]
>
> What's innovative is whoever is running build as root.
>
Well, maybe not if you just download the source and use
the "configure/make/make install" trinity. But when it comes to packaging,
it's another story.
I've been doing RPM packaging for quite a few years. I have been fortunate
enough that my first job was with a Linux distribution (it was called
Mandrake at the time) and, first things first, they taught me how to set up
an RPM environment to build as a regular user.
Believe it or not, but even as of today, in 2009, neither RHEL or its
immediate derivative (CentOS) manage to build a decent set of rules to build
as a non-root user. You have to make your own $HOME/.rpmmacros at the very
least. So, unless you are a skilled enough packager, you cannot even build a
package as a regular user. And some packages out there DO require skills as a
packager to just be built as packages (qmail is one example).
And even as a regular user, and even though you can, say, alter all
of /usr/local to be writeable by someone else than root, I wouldn't be
surprised to hear that a LOT of Linux beginners, seeing that "make install
doesn't work", resort to being root instead. Because it is a known fact that
root can do everything.
Innovative? Not that much.
--
Francis Galiegue
fge@one2team•com
Ingénieur système
Mob : +33 (0) 683 877 875
Tel : +33 (0) 178 945 552
One2team
40 avenue Raymond Poincaré
75116 Paris
next prev parent reply other threads:[~2009-05-09 17:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 9:22 [PATCH v3] To make GIT-VERSION-FILE, search for git more widely Matthias Andree
2009-05-07 11:49 ` Michael J Gruber
2009-05-07 12:04 ` Matthias Andree
2009-05-07 12:09 ` Michael J Gruber
2009-05-07 12:12 ` Matthias Andree
2009-05-08 0:05 ` Junio C Hamano
2009-05-08 8:27 ` Matthias Andree
2009-05-08 8:41 ` Junio C Hamano
2009-05-08 11:09 ` Matthias Andree
2009-05-09 16:55 ` Junio C Hamano
2009-05-09 17:10 ` Francis Galiegue [this message]
2009-05-09 18:17 ` Matthias Andree
2009-05-13 12:17 ` Matthias Andree
2009-05-13 19:32 ` Junio C Hamano
2009-06-02 10:55 ` Nanako Shiraishi
2009-06-02 15:50 ` Junio C Hamano
2009-06-02 18:35 ` Johannes Sixt
2009-06-03 7:32 ` Matthias Andree
2009-06-04 0:12 ` [PATCH v4] " Matthias Andree
2009-06-04 5:18 ` [PATCH v3] " Junio C Hamano
2009-06-04 8:35 ` Matthias Andree
2009-05-08 8:52 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905091910.46775.fge@one2team.com \
--to=fge@one2team$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=matthias.andree@gmx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox