You wrote “It is a myth that arch is unstable”. Arch, being rolling release, is by definition changing. This is, imho, the opposite of stable. This is why it’s important to use precise words. I have no interest in continuing this discussion since you don’t seem to argue in good faith.
You are mistaken about the definition of the word “stable” in the computing context generally.
In the case of both Debian stable and other software which has “stable” releases, it does not mean that there won’t be any updates to the stable release, it means that it was thoroughly tested prior to release and whatever changes might need to be made later can be expected to be relatively minimal and also well tested.
@jobbies@pmk arch means you cannot omit any update. If you do notsync pacman, you will not be able install any package (because they removing old versions from servers very quickly). If you sync pzcman and not update entire system, it will possiboy break on any package installation
deleted by creator
You wrote “It is a myth that arch is unstable”. Arch, being rolling release, is by definition changing. This is, imho, the opposite of stable. This is why it’s important to use precise words. I have no interest in continuing this discussion since you don’t seem to argue in good faith.
You are mistaken about the definition of the word “stable” in the computing context generally.
In the case of both Debian stable and other software which has “stable” releases, it does not mean that there won’t be any updates to the stable release, it means that it was thoroughly tested prior to release and whatever changes might need to be made later can be expected to be relatively minimal and also well tested.
deleted by creator
@jobbies @pmk arch means you cannot omit any update. If you do notsync pacman, you will not be able install any package (because they removing old versions from servers very quickly). If you sync pzcman and not update entire system, it will possiboy break on any package installation
deleted by creator