| 1 |
> If you are installing a package by hand and wants to revert back to |
| 2 |
> the previous state, best is to : |
| 3 |
> |
| 4 |
> - when you ./configure it, use the various --prefix directives (do a |
| 5 |
> ./configure --help for information on that) |
| 6 |
> - when you want to remove, make uninstall in the source dir (so don't |
| 7 |
> remove it!) |
| 8 |
> - if it does not have a remove, usually if you install it inside |
| 9 |
> /home/${username}/whatever, then removing that is fine. |
| 10 |
> |
| 11 |
> Best thing though is to write an ebuild and then Portage will sandbox |
| 12 |
> the build so it knows every file that has been installed. |
| 13 |
> |
| 14 |
> The package knows where to link to when it goes into the ./configure |
| 15 |
> stage and won't act like windows, installing stuffs into registry or |
| 16 |
> the like ... everything's nicely contained inside /lib and /share |
| 17 |
> folders (except /etc files ...which you can safely ignore them there - |
| 18 |
> those are just text files and you'll know where they are anyway if you |
| 19 |
> intend to configure miro) |
| 20 |
|
| 21 |
Thanks everyone. I've never been open to manual compile/installation |
| 22 |
but I can give it a try now. |
| 23 |
|
| 24 |
- Grant |
Archives