public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Installing outside of Portage & cruft removal
Date: Mon, 26 Jan 2009 14:45:08 -0600	[thread overview]
Message-ID: <58965d8a0901261245u783ff4d9gb5d3af9d867fa9f3@mail.gmail.com> (raw)
In-Reply-To: <58965d8a0901261244x22e859a7tdb9234823f7c5c26@mail.gmail.com>

On Mon, Jan 26, 2009 at 2:44 PM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Mon, Jan 26, 2009 at 2:30 PM, Grant <emailgrant@gmail.com> wrote:
>>>> Writing an ebuild is best, but sometimes you just want to give a
>>>> program a try without writing an ebuild (like everyone else running
>>>> Linux does) and a scruft script enables you to do that without making
>>>> a mess of your system.
>>>
>>> Not to be picky, it's just an idea but in that case, isn't it way easier to
>>> just ./configure --prefix=/some/dir/inside/yourhome or edit a makefile?
>>
>> I have to say I know nothing about compiling or installing outside of
>> portage.  Does specifying a prefix like that work?  You get a fully
>> functional program with nothing installed outside of some/dir?
>
> Yes, it's the "normal way" for people that don't use package managers.
> I almost always install into my home directory for programs that
> aren't in portage (or make my own ebuild if it is a simple one). Or
> depending on what program it is, create a user for it and run it under
> that user account so it can't touch anything else.
>
> Also, a lot of more simple programs don't even need to be installed.
> Just untar it, configure it, make it and run it from the directory in
> which the source resides.
>
> Paul
>

I should also say that installing that stuff to /usr/local tree is also normal.



  reply	other threads:[~2009-01-26 20:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 16:41 [gentoo-user] Installing outside of Portage & cruft removal Grant
2009-01-26 16:48 ` Mike Kazantsev
2009-01-26 17:08   ` Jesús Guerrero
2009-01-30 18:45     ` b.n.
2009-01-26 17:35   ` Grant
2009-01-26 17:57     ` Mike Kazantsev
2009-01-26 23:17       ` Neil Bothwick
2009-01-26 17:57     ` Dale
2009-01-26 18:17       ` Grant
2009-01-26 18:26         ` Dale
2009-01-26 19:25         ` Paul Hartman
2009-01-26 20:21           ` Grant
2009-01-26 18:02     ` Rumen Yotov
2009-01-26 18:29     ` Daniel Pielmeier
2009-01-26 20:17       ` Grant
2009-01-26 20:24         ` Jesús Guerrero
2009-01-26 20:30           ` Grant
2009-01-26 20:44             ` Paul Hartman
2009-01-26 20:45               ` Paul Hartman [this message]
2009-01-26 20:51               ` Jesús Guerrero
2009-01-26 22:51                 ` Grant
2009-01-27 14:29                   ` Stroller
2009-01-27 15:29                     ` Hieu, Luu Danh
2009-01-27 22:34                       ` Grant
2009-01-27 22:57                         ` Paul Hartman
2009-01-26 20:44         ` Daniel Pielmeier
2009-01-26 22:31           ` Grant
2009-01-26 19:57     ` Jesús Guerrero
2009-02-15 20:49 ` Alex Schuster
2009-02-16 18:33   ` Grant
2009-02-16 18:41     ` Dirk Heinrichs
2009-02-16 20:31       ` Grant
2009-02-16 20:40         ` [gentoo-user] " Nikos Chantziaras
2009-02-16 20:48           ` Dirk Heinrichs
2009-02-16 20:54             ` Nikos Chantziaras
2009-02-16 21:09               ` Dirk Heinrichs
2009-02-17 18:22                 ` Grant
2009-02-17 18:35                   ` Dirk Heinrichs
2009-02-16 20:43         ` [gentoo-user] " Dirk Heinrichs

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=58965d8a0901261245u783ff4d9gb5d3af9d867fa9f3@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --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