imagemagick name conflict about bash-oo-framework

[nkakouros]

After sourcing the Bash Infinity modules you want (at least the lib/oo-bootstrap.sh file), you can have:

unalias "import"

You can use the . alias to keep using Bash Infinity's import functionality.

[nkakouros]

oo-bootstrap.sh sets three relevant aliases:

alias import="__oo__allowFileReloading=false System::Import"

alias source="__oo__allowFileReloading=true System::ImportOne"

alias .="__oo__allowFileReloading=true System::ImportOne"

The first one can import many files at once, skipping the ones that are already loaded. The other two source a file no matter what.

After sourcing oo-bootstrap.sh, you can:

unalias '.'
alias .="__oo__allowFileReloading=false System::Import"

to have '.' do what 'import' did.

You can do this right after sourcing the bootstrap file.

[ukos-git]

If I understand correctly, I could unalias the import from lib/oo-bootstrap.sh right after using import util/exception.

But I will have to redirect the import binary from imagemagick in the first place. Because now, if I call import after sourcing the file from lib/oo-bootstrap.sh, imagemagick is triggered.

You can use the . alias to keep using Bash Infinity's import functionality.

I did not get that part.

[ukos-git]

You pointed me in the right direction:
instead of

import util/exception

one can use

__oo__allowFileReloading=false System::Import util/exception

[nkakouros]

BTW, this might had been the actual reason for the aliases not working.

[reuvenpo]

Wouldn't

alias .=$(alias import)

or similar, be better than the explicit

unalias '.'
alias .="__oo__allowFileReloading=false System::Import"

?

Will be more robust and less "leaky" in terms of encapsulation too.