You should rather provide a proper debian package for debian/ubuntu users and not install the files directly inside the filesystem. This was never a good idea. #5827

Hmm. I don't know if it was a good idea to automatically uninstall any packages on the system. This is what dependencies and conflicting packages are for. This does not seem useful to me. Maybe you should print some advice that if modemmanager is installed, the user should take care of it.
But I think the way to go was described by @NicoHood already.

Manually merged, the autorun of the script from install.sh has been disabled

Why was this merged? As I said software should not automate any installation or even uninstall software. A proper distribution package should be used instead. Otherwise people with less knowledge will mess up their system and be unable to undo all the changes. I think it was not a wise idea to follow this "concept".

ArduinoCC itself should think of providing debian packages via PPA, as its the most often used distribution at the moment (debian/ubuntu) for end consumer. ArchLinux already has proper packages.

@NicoHood this has been merged since it condenses a lot of FAQs into a "simple" bash script that the user MAY launch if needed. The script is not being launched automatically during installation so it doesn't hurt anyone 😄
About DEB/PPA, I'm sorry I have to repeat it again: it's not something we are willing to provide directly. You did an awesome job with the Arch packages, if someone wants to prepare a deb recipe/a PPA we can endorse it but nothing more.

Those bash commands have to be put into a readme with instruction details and reasons. Users will just try to run it, possibly break their system, dont know what they did and stop. Just write one good doc, but dont automate this. Its evil. But still your opinion.

Actually there are a number of things wrong with arduino-linux-setup.sh!
It is actually dangerous.

1. It shouldn't remove ANY package. It should warn that there may be a problem and suggest how to mitigate it.

2. It very nicely creates a bunch of udev rule files in /tmp but doesn't meet the rule definition - the filename for avrisp.rules is wrong! It is lacking the number at the beginning (should be something like 99-avrisp.rules)

3. It copies ANY file ending in ".rules" from /tmp to /etc/udev/rules.d. WRONG - it should only copy the files it created. Using "*.rules" is a bit too permissive.

4. There is no need to reboot the system. Kicking udev (as done excessively in refreshudev()) is sufficient.

Lastly - there is no documentation regarding arduino-linux-setup.sh! Nothing that tells the user whether or not to run the scrip and if so when. Personally I don't think this file should be part of the distribution at all.

@sk8nfool you are right in all your points.
Now we only need to understand if leaving the file there (and fixing its shortcomings) is worth the effort or if we'd better remove it entirely.
Poll time 🙂 ?