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
The main (default) Ubuntu package repo contains a package named spring (an RTS game interestingly enough, https://github.com/spring/spring/). It would probably be wise for us to not name our package the same as a package available through the main Ubuntu package repo. (I'd be much less worried about clashing with a third party repo)
Besides "bad form", there may be ways to encounter some unexpected behavior because the spring RTS package is version 106.0 ('newer' than our spring 1.0). Something like
will not disturb our package, but either a apt-get --with-new-pkgs upgrade or apt-get dist-upgrade with both remove our spring package and install the RTS game. I'm not significantly familiar with the wide variety of ways to manage packages and upgrades in the Debian & Ubuntu world so there may be other traps we're laying as well.
I think maybe we should use something like antelope-spring for our package name instead.
The text was updated successfully, but these errors were encountered:
The main (default) Ubuntu package repo contains a package named
spring
(an RTS game interestingly enough, https://github.com/spring/spring/). It would probably be wise for us to not name our package the same as a package available through the main Ubuntu package repo. (I'd be much less worried about clashing with a third party repo)Besides "bad form", there may be ways to encounter some unexpected behavior because the spring RTS package is version 106.0 ('newer' than our spring 1.0). Something like
will not disturb our package, but either a
apt-get --with-new-pkgs upgrade
orapt-get dist-upgrade
with both remove our spring package and install the RTS game. I'm not significantly familiar with the wide variety of ways to manage packages and upgrades in the Debian & Ubuntu world so there may be other traps we're laying as well.I think maybe we should use something like
antelope-spring
for our package name instead.The text was updated successfully, but these errors were encountered: