Package — why not "my"?

[kjernekrafttrikk]

I'm kinda newbie in all this free software development, but why did maintainer name his fork the same way — "vesta"?

I mean, when I instal or uninstall myVesta, its name is "vesta". I guess, it's due to compatibility and it won't make notable harm, but as far development will go, the difference will increase, while package still has this name.

Or did I get it wrong?

[Colin1976]

I'm kinda newbie in all this free software development, but why did maintainer name his fork the same way — "vesta"?

I mean, when I instal or uninstall myVesta, its name is "vesta". I guess, it's due to compatibility and it won't make notable harm, but as far development will go, the difference will increase, while package still has this name.

Or did I get it wrong?

In terms of why the maintainer might name their fork "vesta," it’s often done for compatibility reasons. Keeping the same name can make it easier for users to switch between the original and the forked version without changing too many configurations. However, as development progresses, the differences between the original software and the fork can increase, which might make it confusing.

When I needed to navigate similar complexities, Cogniteq provided me with comprehensive support, helping me understand the nuances of software development and management. They could be a valuable resource if you're looking for professional insights and support in this area.