| 1 |
On Tue, Jan 27, 2009 at 4:34 PM, Grant <emailgrant@×××××.com> wrote: |
| 2 |
>> If you are installing a package by hand and wants to revert back to |
| 3 |
>> the previous state, best is to : |
| 4 |
>> |
| 5 |
>> - when you ./configure it, use the various --prefix directives (do a |
| 6 |
>> ./configure --help for information on that) |
| 7 |
>> - when you want to remove, make uninstall in the source dir (so don't |
| 8 |
>> remove it!) |
| 9 |
>> - if it does not have a remove, usually if you install it inside |
| 10 |
>> /home/${username}/whatever, then removing that is fine. |
| 11 |
>> |
| 12 |
>> Best thing though is to write an ebuild and then Portage will sandbox |
| 13 |
>> the build so it knows every file that has been installed. |
| 14 |
>> |
| 15 |
>> The package knows where to link to when it goes into the ./configure |
| 16 |
>> stage and won't act like windows, installing stuffs into registry or |
| 17 |
>> the like ... everything's nicely contained inside /lib and /share |
| 18 |
>> folders (except /etc files ...which you can safely ignore them there - |
| 19 |
>> those are just text files and you'll know where they are anyway if you |
| 20 |
>> intend to configure miro) |
| 21 |
> |
| 22 |
> Thanks everyone. I've never been open to manual compile/installation |
| 23 |
> but I can give it a try now. |
| 24 |
|
| 25 |
Once you learn the basics, most programs are the same (configure/make) |
| 26 |
and it's not so bad. Obviously the advice to read the README/INSTALL |
| 27 |
files is golden, they will almost always tell you what you need to |
| 28 |
know. |
| 29 |
|
| 30 |
On my home PC I used to tri-boot OS/2 (my first love), Win95 |
| 31 |
(wintendo) and Slackware (version 2 or 3?), so back then I think |
| 32 |
everything had to be manually configured and compiled pretty much. I |
| 33 |
guess it all seems kind of obvious once you already know how to do it. |
| 34 |
We've come a long way since then. :) |
Archives