Re: Moving wip to Subversion

[Pippijn van Steenhoven <pip88nl%gmail.com@localhost>]

Eric Schnoebelen wrote:

> grant beattie writes:
> - one small usage example is that if wip were in !cvs, the convenience
> - of having "cvs update" in pkgsrc/ also update the wip/ directory would
> - be lost. that's a reasonable downside, imho.
> 
> I'm not sure loosing this capability is a reasonable
> downside for me.  Having wip under pkgsrc (and suitable keys)
> allows me to update both trees that I'm using software out of
> with one ``cvs update'' command. [..]

In my opinion, the migration from CVS to Subversion should be carefully
planned and prepared. I think best would be to migrate both pkgsrc-wip and
the rest of the NetBSD sources to Subversion at the same time. One thing
that caused me to think was, what sjamaan said in #netbsd on freenode about
Subversion, that SVN repositories keep every file twice which could make
current filesystems to run out of i-nodes. "It's new" is not a feature at
all because you could in the same breath say "It's untested". The two
features I really like are 1) directories are tagged and 2) commit takes
effect only after the full commit has been done by tagging commits rather
than files.
Greetings, Pippijn



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss