I would like to see pkgsrc-wip community opinion on switching the
tracker from CVS to something more convenient.
I have just found OpenBSD ports wip runs on git
(http://gitorious.org/openbsd-ports-wip).
Well, CVS works and can work for another couple of years. But I believe
CVS may be just the most putting off issue for many new potential pkgsrc
contributors (and there is definitely a lack of them!).
Indeed CVS still works. I have switched to git for some things, and
find that
+ merging
+ working offline
+ letting non-committers contribute within the tool
- hard to understand
* people who don't get git yet will avoid projects in git
In pkgsrc-wip
we don't do merges
offline work would typically be "spiff up some package, and commit it
when back to the net", and
pretty much anyone can get a commit bit
almost everyone using pkgsrc-wip deals with real pkgsrc which is in
CVS, which means they already have CVS running and understand it
** no one has articulated any problems getting work done in wip within
CVS **
so for now I don't see any advantage in switching. When pkgsrc changes
to a different tool, pkgsrc-wip following would make sense.
You said "more convenient". Could you explain what you are doing now
that's hard in CVS that would be easier in git?
Attachment:
pgpIzGU4AD9vv.pgp
Description: PGP signature
------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm
_______________________________________________ pkgsrc-wip-discuss mailing list pkgsrc-wip-discuss%lists.sourceforge.net@localhost https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss