1 |
On Mon, January 26, 2009 21:44, Paul Hartman wrote: |
2 |
> On Mon, Jan 26, 2009 at 2:30 PM, Grant <emailgrant@×××××.com> wrote: |
3 |
>>>> Writing an ebuild is best, but sometimes you just want to give a |
4 |
>>>> program a try without writing an ebuild (like everyone else running |
5 |
>>>> Linux does) and a scruft script enables you to do that without making |
6 |
>>>> a mess of your system. |
7 |
>>> |
8 |
>>> Not to be picky, it's just an idea but in that case, isn't it way |
9 |
>>> easier to |
10 |
>>> just ./configure --prefix=/some/dir/inside/yourhome or edit a makefile? |
11 |
>> |
12 |
>> I have to say I know nothing about compiling or installing outside of |
13 |
>> portage. Does specifying a prefix like that work? You get a fully |
14 |
>> functional program with nothing installed outside of some/dir? |
15 |
> |
16 |
> Yes, it's the "normal way" for people that don't use package managers. |
17 |
> I almost always install into my home directory for programs that |
18 |
> aren't in portage (or make my own ebuild if it is a simple one). Or |
19 |
> depending on what program it is, create a user for it and run it under |
20 |
> that user account so it can't touch anything else. |
21 |
|
22 |
Yes. It's mostly that simple. Though sometimes in more complex programs |
23 |
you might need some extra setup (i.e. configure some variable so the program |
24 |
can find its path to the required libs or so). It really depends on the |
25 |
program, |
26 |
however if you open the readme or install file and take a look 99% of the |
27 |
times the procedure should be described there. Not all programs use the |
28 |
tipical make system, so you should always check the docs, and in any case |
29 |
save the source tree for further refference, or just to be able to make |
30 |
uninstall. |
31 |
|
32 |
Note that this is the cleanest method, and in some cases it's the only option |
33 |
(i.e. you don't have root access to the machine, so you have to build in your |
34 |
home dir). |
35 |
|
36 |
> |
37 |
> Also, a lot of more simple programs don't even need to be installed. |
38 |
> Just untar it, configure it, make it and run it from the directory in |
39 |
> which the source resides. |
40 |
|
41 |
This work for smaller programs very well. Just make and launch it. |
42 |
|
43 |
-- |
44 |
Jesús Guerrero |