public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Slade <krakrjak@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] What about a new file system subtree?
Date: Sat, 18 Feb 2006 10:08:42 -0600	[thread overview]
Message-ID: <200602181008.42559.krakrjak@volumehost.net> (raw)
In-Reply-To: <200602181716.18524.info@maestroprogramador.com>

On Saturday 18 February 2006 10:16, Rafael Fernández López wrote:
> > This is what --prefix is for.
> > ./configure --prefix=~/
> > make && make install
> > This puts it into /home/user/ where /home/user is considered to be /

> 	What I meant is that it could be selected as default option. My idea is to
> make easier new users to install apps that don't have, and that would like
> to, without having to read man configure.
This is the pneumonic load of *nix.  Installing software is non-trivial.  We 
make it much easier in gentoo with emerge, just as autoconf/automake made it 
much simpiler in the past.  If a user is going to compile and install 
software in their home directory they are going to have to at least learn 
--prefix as an option to configure.  Fortunately/unfortunately this is a 
requirement.  Just as learning to use ls to list files in a directory.
-- 
Zac Slade

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-18 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18 15:52 [gentoo-user] [OT] What about a new file system subtree? Rafael Fernández López
2006-02-18 15:44 ` Zac Slade
2006-02-18 16:16   ` Rafael Fernández López
2006-02-18 16:08     ` Zac Slade [this message]
2006-02-18 16:22     ` Rafael Bugajewski
2006-02-18 15:50 ` Devon Miller
2006-02-18 15:50 ` Rafael Bugajewski
2006-02-18 16:20   ` Rafael Fernández López
2006-02-18 16:11     ` Zac Slade
2006-02-21  4:16 ` David Mallwitz

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=200602181008.42559.krakrjak@volumehost.net \
    --to=krakrjak@volumehost.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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