]>
Commit | Line | Data |
---|---|---|
1 | Summary: Bazaar-NG - a changeset oriented revision control system | |
2 | Summary(pl): Bazaar-NG - system kontroli wersji zorientowany na zestawy zmian | |
3 | Name: bzr | |
4 | Version: 0.13 | |
5 | Release: 1 | |
6 | License: GPL v2 | |
7 | Group: Development/Version Control | |
8 | Source0: http://bazaar-vcs.org/releases/src/%{name}-%{version}.tar.gz | |
9 | # Source0-md5: 14278ee54bef1cf65ee13735b134f9dd | |
10 | Patch0: %{name}-FHS.patch | |
11 | URL: http://bazaar-vcs.org/ | |
12 | BuildRequires: python >= 1:2.4 | |
13 | BuildRequires: rpmbuild(macros) >= 1.219 | |
14 | %pyrequires_eq python | |
15 | Requires: python-cElementTree | |
16 | Requires: python-pycurl | |
17 | Requires: python-Crypto | |
18 | BuildArch: noarch | |
19 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) | |
20 | ||
21 | %description | |
22 | Bazaar-NG (aka bzr, later to be named Bazaar 2) is a community project | |
23 | led by canonical to develop a free software distributed revision | |
24 | control system that is powerful, friendly, scalable and easy to use. A | |
25 | revision control system is a tool that developers and system | |
26 | administrators use to keep track of the changes to files over time. | |
27 | Additionally, a revision control system such as Bazaar-NG eases the | |
28 | burdens of working together in teams. | |
29 | ||
30 | Bazaar-NG is a changeset oriented revision control system. Changeset | |
31 | oriented revision control systems collect the logically related | |
32 | changes to individual files together into one cohesive group which | |
33 | typically represent a bug fix or a new feature. These changesets are | |
34 | easily transferred from one branch to another with simple to use | |
35 | commands like "bzr pull" and "bzr branch". | |
36 | ||
37 | Bazaar-NG is also a distributed revision control system. A distributed | |
38 | revision control such as Bazaar-NG not only allows a project to have | |
39 | multiple branches, but users to have multiple private branches as | |
40 | well. Bazaar-NG makes it easy for users to make a branch that is based | |
41 | off of another branch, make changes and then later merge the branches | |
42 | back together. Importantly, the general public can make a new branch | |
43 | based upon an authoritive branch of a project, fix one or more things | |
44 | and then offer the branch back to the upstream for merging. Bazaar-NG | |
45 | also supports the sharing of branches between developers. | |
46 | ||
47 | %description -l pl | |
48 |