Remove "Prefer/force IPv4 for apt" #2752
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I can understand the original intention, autonomous systems had issues with the current Internet Protocol a.k.a. IPv6 over the past years but this protocol is now very well established, mature and, IMO, there is no reason to a single application dictates how an operating system (or package manager in this regard) will behave regarding the system's Internet connectivity especially if the target environment has no issues with it and, if the opposite, masks any ongoing issue particular to the host OS, ISP and/or the server on the other end. Circumventing things in the intention to get them done quick does not fix the root cause and it's better to put the effort once to fix things in a definitive way than sweeping it under the carpet to deal with it later and over and over. Any application shouldn't touch anything external to and/or broader than its own scope unless it's strictly necessary and the user is aware of any change & acknowledges it. Signed-off-by: Anderson Silva <UnderEu@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I can understand the original intention, autonomous systems had issues with the current Internet Protocol a.k.a. IPv6 over the past years but this protocol is now very well established, mature and, IMO, there is no reason to a single application dictates how an operating system (or package manager in this regard) will behave regarding the system's Internet connectivity especially if the target environment has no issues with it and, if the opposite, masks any ongoing issue particular to the host OS, ISP and/or the server on the other end.
Circumventing things in the intention to get them done quick does not fix the root cause and it's better to put the effort once to fix things in a definitive way than sweeping it under the carpet to deal with it later and over and over. Any application shouldn't touch anything external to and/or broader than its own scope unless it's strictly necessary and the user is aware of any change & acknowledges it.