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