Re: FWD: [Bug#528733: O: svn-buildpackage -- helper programs to maintain Debian packages with Subversion]
On Fri, May 15, 2009 at 04:15:29PM +0200, Manuel Prinz wrote:
> just to clarify:
Me too. ;-)
>
> Am Freitag, den 15.05.2009, 13:41 +0200 schrieb Andreas Tille:
> > Please try not to turn this thread into an Emacs-agains-Vim-ish flamewar
> > about the "best" VCSs. There is no such thing like a best VCSs
>
> This was not my intent at all! I agree with you that the choice of a VCS
> is personal preference. I neither want force the use of my pet-VCS.s
This remark was not targeted to you - just general for the users of
this list.
> My
> intent was to have a session to just talk about experiences with other
> VCSs. I never used bazaar, mercurial or darcs
Me neither - and I see no point in spending my time if so many others
just did.
> for packaging but obviouly
> people do and feel quite happy about that.
Not that I know of from anybody on this list.
> I'd be interested in hearing
> their point of view as well, trying to understand if there are similar
> workflows or why they prefer those over a different VCS. This does not
> have to end in a flamewar at all; it's perfectly possible to just listen
> to peoples' concerns/opions. As long as noone tries to "force opions" on
> others, it's just tech-talk. And understanding these point of views
> probably helps making better choices (if there is a need).
I'm not against a tech talk. But the Debian Med list is just not
a proper forum for this talk. As far as I know people here SVN is
very common and other people tend to Git. Anybody who disagrees
with this statement is welcome to raise his voice but if he is not
able why a certain VCS is especially useful for packaging medical
application I would love to see the discussion on a different place.
I'm afraid that some users might loose their nerves about this
kind of tech talk. I did not intend to suppress any opinion (even
if I admit my last mail might have sounded like this).
> It's possible to do packaging in Git with the "debian/ + tarball" model
> as well, as it is with SVN. But it's exactly these concerns that not
> everyone using Git may be aware of;
Well, I'm aware of this. But all Git experts I talked to that
the typical workflow with Git is taking over the whole pristine
source. So *if* I want something else like SVN why than using
it as if it would be SVN. Feel free to prove me (or those to
who I asked about Git) wrong - I'd be happy if I'm mistaken about
this idea of workflow.
> so my suggestion would be to put our
> heads together and try to understand those issues better. I'm quite
> confident noone will get hurt. ;)
It is fine for me to work out a reasonable Git policy for our
group and also discuss this issue. But I'd prefer to focus
on things who are widely adopted in Debian and the discussion
might take place on the maintainers mailing list on Alioth
to not blur this list to much.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: