From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on sa.int.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.2.5 Date: Sun, 15 Feb 2009 23:22:39 +0200 From: Igor Vlasenko To: ALT Linux Team development discussions Message-ID: <20090215212239.GA14515@dad.imath.kiev.ua> References: <20090213161847.GB11969@wo.int.altlinux.org> <20090214185538.GA15638@dad.imath.kiev.ua> <20090214202304.GG31985@altlinux.org> <20090214210458.GB17284@dad.imath.kiev.ua> <20090214212254.GJ31985@altlinux.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090214212254.GJ31985@altlinux.org> User-Agent: Mutt/1.5.18 (2008-05-17) Received-SPF: pass (dad.imath.kiev.ua: domain of vlasenko@dad.imath.kiev.ua designates 127.0.0.1 as permitted sender) receiver=dad.imath.kiev.ua; client-ip=127.0.0.1; helo=dad.imath.kiev.ua; envelope-from=vlasenko@dad.imath.kiev.ua; x-software=spfmilter 0.95 http://www.acme.com/software/spfmilter/ with libspf2; Subject: Re: [devel] acl file missing: a trouble for repocop X-BeenThere: devel@lists.altlinux.org X-Mailman-Version: 2.1.10b3 Precedence: list Reply-To: ALT Linux Team development discussions List-Id: ALT Linux Team development discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2009 21:22:43 -0000 Archived-At: List-Archive: List-Post: On Sun, Feb 15, 2009 at 12:22:54AM +0300, Alexey Tourbin wrote: > Some time ago, the only possibility for testing was post-processing. > Recently, things have changed. Now there's a (still rather limited) > possibility for pre-processing, PROVIDED that your checks can detect > important issues and PROVIDED your code does not take too much time. > > That is to say, there's a real shift. Something can be a pre-condition, > not a post-condition as it used to be. > > Here is a clue: think of how you can integrate certain parts of your > code directly into girar-builder. This is not impossible. Dmitry already did it well. http://git.altlinux.org/tasks/xxx/plan/ has a list of added/removed packages. http://git.altlinux.org/tasks/xxx/build/? has new packages themselves. The only thing left in girar that we need for integration is a passive notifier, i.e. some kind of robot-friendly list of successively completed tasks. I think it is preferred and unix-way. I think any kind of active notifier (some script that runs after a task has completed and either tries to launch repocop directly or tries to send it a message) will add an extra complexity to girar builder and will make both of them less scalable and maintainable. repocop is 90% ready to work in the described mode, exept the patch generator which still need some imnprovement. -- Dr. Igor Vlasenko -------------------- Topology Department Institute of Math Kiev, Ukraine