Search Results for "upgrading"

...They’re also specifications (or specs, for short): detailed explanations of how the application is supposed to behave, expressed in plain English. RSpec follows semantic versioning, which means that “major version” upgrades (e.g., 2.x → 3.x) come with breaking changes. If you’re upgrading from version 2.x or below, read the rspec-rails upgrade notes to find out what to watch out for. In RSpec, assertions are called expectations, and every expectation is built around a matcher. When you expect(a).to eq(b), you’re using the eq matcher. RSpec Rails defines ten different types of specs for testing different parts of a typical Rails application. ...

...With pkg_version-zypper.rb script you can first see a nice list of package statuses and ignore packages' minor versions (eg. from version 1.2.3-1.2 to 1.2.3-1.3) when upgrading your software. In daily usage basis, this enables to avoid re-installing tens and tens of programs for no big reason (usually) and do it only when programs in repository has been updated. NB! It is not an official recommendation to do so as packages have their version number for a reason! I personally have been ignoring RPM versions for years and have not been into any trouble because of that. ...