Re: [devel] acl file missing: a trouble for repocop

["Dmitry V. Levin" <ldv@altlinux.org>]

[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]

On Sun, Feb 15, 2009 at 12:22:54AM +0300, Alexey Tourbin wrote:
> On Sat, Feb 14, 2009 at 11:04:58PM +0200, Igor Vlasenko wrote:
> > On Sat, Feb 14, 2009 at 11:23:04PM +0300, Alexey Tourbin wrote:
> > > On Sat, Feb 14, 2009 at 08:55:38PM +0200, Igor Vlasenko wrote:
> > > > On Fri, Feb 13, 2009 at 07:18:47PM +0300, Dmitry V. Levin wrote:
> > > > > Subject: [#874] COMPLETE sisyphus_check.git=0.8.9-alt1
> > > > обновил, запустил,
> > > > 
> > > > и кстати вытоптал грабли:
> > > > can't open acl file /home/repocop/Sisyphus/files/list/list.src.classic: No such file or directory at /usr/lib/perl5/vendor_perl/Test/Repocop/ALTLinuxACL.pm line
> > > > 
> > > > где теперь можно найти файл текущих acl в виде,
> > > > дружествнном к роботу?
> > > 
> > > What kind of tests have to deal with ACL, and why do you think
> > > that ACL thing is important for automated post-processing?
> > 
> > отчеты по тестам. С разбивкой согласно acl.
> 
> 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.

Strictly speaking, there is a little pre-processing tool we use
for a long time already: sisyphus_check.  All the rest is true.


-- 
ldv

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]