Add some small advise about module's update

[uzluisf]

The problem

After struggling for half an hour with a change to a local module that wasn't being reflected,
I realized that I needed to uninstall and install the local module again for the change to take place.

If this is mentioned somewhere else, this can be disregarded.

Solution provided

Point out that one must uninstall and install a given local module for the latest changes to take place.

[zoffixznet]

👍 Thanks!

[ugexe]

This isn't entirely true. You can force install ( part of the CompUnit::Repository api ), change the auth, or bump the version or api.

I would go one step further and say if you are doing development on a module such that you are changing the code without getting around to bumping the version that you should just be using -I. ( or -Ilib ) which would put the targeted repo in front of the other installation repos.

[zoffixznet]

After struggling for half an hour with a change to a local module that wasn't being reflected,

What was the problem, actually? Doesn't zef say "already installed" and refuses to install again?

[uzluisf]

@ugexe Thanks for the advice. I'll look into the CompUnit::Repository api.

@zoffixznet
It was more of a problem from my lack of knowledge. The thing is that I installed the local module, made some changes to it afterward but when I proceeded to use it, none of those changes were reflected. I decided to uninstall and then install the module again with the latest changes. However, that doesn't seem to be the most appropriate course of actions as per @ugexe's suggestion.

[zoffixznet]

I reworded the text to address both ugexes comments and to reduce the chances of the problem that happened to you happening to users.

[uzluisf]

That addresses my concern. Thanks!