Re: tomcat5.5, 6.0 and version control
On 11/14/06, Marcus Better <marcus@better.se> wrote:
[...]
No, only the source will be under version control. The orig.tar.gz is still
the same.
OK.
I really think that the packaging methods we use are impairing the package
quality. I've examined the patches in several packages, and found problems
that were not spotted, probably because they were hidden in a patch with a
vague name and undocumented purpose. Version control would help here.
Maybe you are right.
> Are you suggesting here that Subversion is not a version control system
> with "proper merging support"?
The limitations of Subversion are well known [1]. Still it is possible to
work with multiple branches, once you learn the manual bookkeeping. I've
documented my preferred method [2]. My suggestion was to use a VCS that
keeps track of merges automatically (for new packages).
Choice of VCS is a matter of taste, but I don't see why a diverse project
like pkg-java project should be constrained to svn only.
You are right. I must say that I only practice CVS and subversion and
I don't know other VCS. Also, I must admit I don't really have the
time to learn one more because at the moment, subversion fills all my
needs.
[2] http://pkg-tikiwiki.alioth.debian.org/
I'll have a look at this link.
Also, of course, choose the VCS you want if you start a new package,
but the problem I see is you'll be the only one to work on the
package. And in my POV, it's a problem in pkg-java and in Debian in
general. Now, if the VCS is really useful and those who wants to help
don't have to learn 1K documentation, it's ok.
--
Arnaud Vandyck
Reply to: