cvs commit: ports/databases/mariadb-client Makefile distinfo pkg-descr pkg-message pkg-plist ports/databases/mariadb-client/files mysql-server.in patch-extra::yassl::src::yassl_error.cpp patch-sql::mysqld.cc ports/databases/mariadb-scripts Makefile ...

[Doug Barton]

On 06/02/2011 03:41, Alexey Dokuchaev wrote:
> * Doug Barton wrote:
>> These aren't ready for use yet, just checking in my WIP
>
> I think this is not the best way to deal with long porting efforts.
> Sure it's very tempting to use version control for anything more
> complicated that "hello world" type of work, but it this case local hg
> or git mirror would suit much better.
>
> Last by not least, end users probably won't expect WIP in the ports: if
> something's committed, it should work, if it does not, it is broken, not
> "in progress".  I believe our CVS should not be abused for private works
> (private here means "behind the scenes").

First, the ports were marked IGNORE when I did the forced commit to 
acknowledge the repo-copy, so I don't think I am violating any user 
expectations here.

Second, under normal circumstances I would agree with you, however the 
effort to split these ports has been more than I (foolishly? 
optimistically?) anticipated, so my usual method of committing the new 
version in one fell swoop wasn't going to be as easy as I had hoped. By 
clearing away the debris it makes it a lot easier for me to actually 
finish the work. All in all I think it's a net win, but I allow that 
reasonable minds can differ on this topic.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/