Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Apr 2001 13:24:26 -0400 (EDT)
From:      mi@aldan.algebra.com
To:        Maxim Sobolev <sobomax@FreeBSD.org>
Cc:        Will Andrews <will@physics.purdue.edu>, ports@FreeBSD.org
Subject:   Re: requesting enhancements to addport :)
Message-ID:  <200104181724.f3IHORC36692@misha.privatelabs.com>
In-Reply-To: <3ADDC64B.F23B4403@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 18 Apr, Maxim Sobolev wrote:
= mi@aldan.algebra.com wrote:
= 
= > On 18 Apr, Will Andrews wrote:
= > = On Wed, Apr 18, 2001 at 09:08:53AM -0400, Mikhail Teterin wrote:
= > = > 1. Making the port addition and module list modification in a single
= > = >    commit (transaction).
= > =
= > = That will tax most people's Internet connections needlessly.
= >
= > Compare the taxation of the  single committer during the commit with
= > the taxing  brought by an  extra e-mail message  to cvs sent  to all
= > subscribers.
=
= Well, gziped CVSROOT/modules currently is  55KB long (transfer size is
= 110KB, because file  have to be transferred to and  then from client),
= so dialup committers would kill  you.... In addition, it would greatly
= increase possibility of stale lock on CVSROOT/modules (Bad Thing, BTW)
= due to dualup going down in the middle of transfer.

Mmm, indeed,  I did  not think  about this one...  May be  the e-mailing
scripts should  be improved to  address my  concern, then, but  that's a
whole  different story...

Or, wait,  should not the modules  update be automaticly triggered  by a
port addition  (commitinfo/taginfo/...)? This would ensure  the database
consistency without the ill-effect you describe below.

Modifying the  modules can  be done  by direct use  of ci/co/rcs  or the
processing scripts should  be taught to avoid the  useless message which
echo each port addition.

= > In  addition to  the simple  database management  consideration: all
= > pieces of a  transaction should be committed at once  -- to simplify
= > logging and roll-back, and ensure consistency...
=
= I'm objecting  to this. In addition  to a valid arguments  supplied by
= the  Will  and my  arguments  above  in  your  scheme cvs  history  of
= CVSROOT/modules will  be bloated with unnecessary  description of each
= port added.

Indeed...

	-mi 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104181724.f3IHORC36692>