Fossil (software)
| fossil
|
|
|---|---|
|
|
| Basic data
|
|
| developer | D. Richard Hipp et al. a. |
| Current version |
2.11 ( May 25, 2020 ) |
| operating system | unix-like systems ( Linux , OpenBSD , macOS ), Microsoft Windows |
| programming language | C. |
| category | programming |
| License | BSD license |
| German speaking | No |
| https://fossil-scm.org/ | |
Fossil is a free distributed version control (SCM) system for software similar to Bazaar , BitKeeper , Git , Mercurial and Monotone .
properties
The name Fossil indicates a key feature of the system: All changes made should be traceable forever. Fossil does not use sequential version numbering (like CVS and Subversion ) to keep track of versions, but calculates a unique hash value for each commit (like the other distributed systems). This is necessary because there is not necessarily a central repository for version management, each user creates his own local repository. Changes are clearly identifiable and versionable through the hash value. However, as with the other distributed version managements, a central server is possible in order to synchronize the individual versions. Also Branches , Tags and Mergen dominated fossil.
construction
A fossil repository consists of a single file that can also be used as a web server using the fossil program . This goes beyond a pure SCM , it also contains functions that are otherwise known from integrated platforms such as GitHub and Bitbucket :
- Integrated wiki
- Integrated forum
- Integrated bug tracker
The integration of these three functions and the consolidation of the data for a project in a single file result in particular advantages.
- Several different systems do not have to be coordinated and connected to one another.
- “Moving” to another computer simply means moving a single file.
- Not only the source code of the project (as with the other distributed version management), but also the wiki, bug tracker and forum can be accessed offline (i.e. without a connection to a central server) and changes can be synchronized again later.
In addition, the use of SQLite for data storage has the advantage of a fully documented storage format and full compliance with the ACID criteria.
Compatibility with Git
A complete import and export of a repository including its history from and to Git is available and - from Fossil 2.9 - can also be automated. However, this does not apply to wiki and bug tracking; an export would be possible here by accessing the SQLite database.
distribution
The following major projects use Fossil:
Web links
Individual evidence
- ↑ www.fossil-scm.org .
- ^ Fossil / Import And Export. Retrieved December 2, 2019 .