You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, firstly, thanks for providing this tool - it's a great little time saver! I have a slightly annoying request, though: would you consider changing the name to something that doesn't clash with GNU AutoGen?
One problem with the current name is that it's very tempting to sudo apt-get install autogen which installs the 22-year-old GNU AutoGen tool rather than your package. I've made this mistake myself and wasted some time puzzling over why none of the example autogen invocations from your docs worked. I know at least a couple of colleagues who've made the exact same mistake, so it can't just be me!
If you're not willing to change the name, can I suggest adding a note to the README warning users about this?
The text was updated successfully, but these errors were encountered:
Hi @alimuldal — thanks for the note! Sorry for the confusion. I will look into renaming it, but will need to carefully add backwards-compatibility to make sure existing users aren't broken by it. I know some folks have hard-coded the GitHub repo path and script names, but thankfully, GitHub forwards renamed repos, so this should be feasible to do.
In the short-term, I will add a note to the README as you suggested.
Hello, firstly, thanks for providing this tool - it's a great little time saver! I have a slightly annoying request, though: would you consider changing the name to something that doesn't clash with GNU AutoGen?
One problem with the current name is that it's very tempting to
sudo apt-get install autogen
which installs the 22-year-old GNU AutoGen tool rather than your package. I've made this mistake myself and wasted some time puzzling over why none of the exampleautogen
invocations from your docs worked. I know at least a couple of colleagues who've made the exact same mistake, so it can't just be me!If you're not willing to change the name, can I suggest adding a note to the README warning users about this?
The text was updated successfully, but these errors were encountered: