Allow uninstall/remove of a given package

[UnixJunkie]

Hello,

I know you don't like the overall added complexity, but that would be so nice.

Some packages, like the excellent parmap do have an uninstall target in their Makefile. So, for some packages, odb could just try calling the corresponding target, if any.

This would be a start and still better than nothing.

If you could provide some hints/doc if someone wants to implement a complete uninstall command, that could be helpful too.

Best regards, F.

[thelema]

L448 has an uninstall function. At the moment it's pretty simple, but you can try to use a package-provided uninstall target in addition to the existing code, that would be fine.

[UnixJunkie]

Hello,

In fact, this issue is completely related to issue #46.

I would like to add the possibility to specify custom commands to configure/build/install/uninstall a package describbed in the ~/.odb/packages file (in fact it would be nice if it can also handle broken oasis packages).

The goal is that the working programmer has an escape route in case some package/library fail to install using the default odb.ml method (for whatever reasons, like a patch is needed before compilation or the oasis package is broken and your correcting patch is not yet accepted, etc.).

So, in that case the working programmer can specify a rule to override any of the package install steps: configure/build/install/uninstall.

Do you think it would be useful?

Do you have some special recommendations before I start working on this?

Thanks a lot, F.

[thelema]

On 05/18/2012 12:40 AM, Francois Berenger wrote:

Hello,

In fact, this issue is completely related to issue #46.

I would like to add the possibility to specify custom commands to configure/build/install/uninstall a package describbed in the ~/.odb/packages file (in fact it would be nice if it can also handle broken oasis packages).

The goal is that the working programmer has an escape route in case some package/library fail to install using the default odb.ml method (for whatever reasons, like a patch is needed before compilation or the oasis package is broken and your correcting patch is not yet accepted, etc.).

So, in that case the working programmer can specify a rule to override any of the package install steps: configure/build/install/uninstall.

Do you think it would be useful?

Do you have some special recommendations before I start working on this?

In the use case you seem to be describing, odb's ability to install from local packages/directories seems sufficient. If you want to patch some library before installing it, do so - create the patched library, and add an entry to your packages file saying where that library is, and odb will use that copy instead of upstream.

E.