1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
<nowiki>
<h1 align="center">Questions And Criticisms</h1>
<p>This page is a collection of real questions and criticisms that have been
raised against fossil together with responses from the program's author.</p>
<b>Fossil sounds like a lot of reinvention of the wheel.
Why create your own DVCS when you could have reused mercurial?</b>
<blockquote>
I wrote it because none of the
other available DVCSes met my needs. If the other DVCSes do
meet your needs, then you probably do not need fossil. But they
don't meet mine, and so fossil is necessary for me.
Feature provided by fossil that one does not get with other
DVCSes:
<ol>
<li> Integrated <a href="wikitheory.wiki">wiki</a>. </li>
<li> Integrated <a href="bugtheory.wiki">bug tracking</a> </li>
<li> Immutable artifacts </li>
<li> self-contained, stand-alone executable </li>
<li> simple, well-defined,
|
|
|
|
|
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
<nowiki>
<h1 align="center">Questions And Criticisms</h1>
<p>This page is a collection of real questions and criticisms that have been
raised against fossil together with responses from the program's author.</p>
<b>Fossil sounds like a lot of reinvention of the wheel.
Why create your own DVCS when you could have reused mercurial?</b>
<blockquote>
<p>I wrote fossil because none of the
other available DVCSes met my needs. If the other DVCSes do
meet your needs, then you might not need fossil. But they
don't meet mine, and so fossil is necessary for me.</p>
<p>Feature provided by fossil that one does not get with other
DVCSes include:</p>
<ol>
<li> Integrated <a href="wikitheory.wiki">wiki</a>. </li>
<li> Integrated <a href="bugtheory.wiki">bug tracking</a> </li>
<li> Immutable artifacts </li>
<li> self-contained, stand-alone executable </li>
<li> simple, well-defined,
|
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
<p>I take a pragmatic approach to software: form follows functions.
To me, it is more important to have a highly reliable, fast, efficient,
enduring, and simple DVCS than one that looks pretty.</p>
<p>On the other hand, if you have patches that improve the apparance
of Fossil without seriously compromising its reliablity, performance,
an maintainability, I will be happy to accept them. Fossil is
self-hosting. Write to the maintainers for a password that will let
you push to the main fossil repository.</p>
</blockquote>
<b>It would be useful to have a separate application that
keeps the bug-tracking database in a versioned filed. That file can
then be pushed and pulled along with the rest repository.</b>
<blockquote>
<p>This addressed in the opening paragraphs of
the <a href="bugtheory.wiki">Bug-Tracking In Fossil</a> document.
</blockquote>
<b>Fossil is already the name of a plan9 versioned
append-only filesystem.</b>
<blockquote>
I did not know that. Perhaps they choose the name for the same reason that
I did: because a repository with immutable artifacts preserves
and excellent fossil record of a long-running project.
</blockquote>
<b>The idea of storing a repository in a binary blob like an
SQLite database terrifies me.</b>
|
|
|
|
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
<p>I take a pragmatic approach to software: form follows functions.
To me, it is more important to have a highly reliable, fast, efficient,
enduring, and simple DVCS than one that looks pretty.</p>
<p>On the other hand, if you have patches that improve the apparance
of Fossil without seriously compromising its reliablity, performance,
an maintainability, I will be happy to accept them. Fossil is
self-hosting. Send me email to request a password that will let
you push to the main fossil repository.</p>
</blockquote>
<b>It would be useful to have a separate application that
keeps the bug-tracking database in a versioned filed. That file can
then be pushed and pulled along with the rest repository.</b>
<blockquote>
<p>This addressed in the opening paragraphs of
the <a href="bugtheory.wiki">Bug-Tracking In Fossil</a> document.
</blockquote>
<b>Fossil is already the name of a plan9 versioned
append-only filesystem.</b>
<blockquote>
I did not know that. Perhaps they selected the name for the same reason that
I did: because a repository with immutable artifacts preserves
and excellent fossil record of a long-running project.
</blockquote>
<b>The idea of storing a repository in a binary blob like an
SQLite database terrifies me.</b>
|
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
|
directly in the VCS - either they are under-featured compared to full
software like Trac, or the VCS is massively bloated compared to
Subversion or Bazaar.</b>
<blockquote>
<p>I have no doubt that Trac has many features that fossil lacks. But that
is not the point. Fossil has several key features that Trac lacks and that
the primary fossil author cannot live without: most notably the fact that
<p>As for bloat: Fossil is a single fully self-contained executable.
You do not need any external packages in order to run fossil. You do not
need diff, patch, merge, cvs, svn, rcs, python, perl, tcl, sqlite, or anything
else in order to run fossil. Fossil runs just fine in a chroot jail all
by itself. And the self-contained executable is much less than 1MB in size.
|
|
|
|
|
>
|
|
>
|
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
directly in the VCS - either they are under-featured compared to full
software like Trac, or the VCS is massively bloated compared to
Subversion or Bazaar.</b>
<blockquote>
<p>I have no doubt that Trac has many features that fossil lacks. But that
is not the point. Fossil has several key features that Trac lacks and that
I cannot live without: most notably the fact that
fossil supports disconnected operation.</p>
<p>As for bloat: Fossil is a single self-contained executable.
You do not need any other packages
(diff, patch, merge, cvs, svn, rcs, git, python, perl, tcl, apache,
sqlite, and so forth)
in order to run fossil. Fossil runs just fine in a chroot jail all
by itself. And the self-contained fossil
executable is much less than 1MB in size.
Fossil is the very opposite of bloat.</p>
</blockquote>
</nowiki>
|