Re: Unmarked conflict checking in portcheck

2014-07-24 Thread Christian Weisgerber
On 2014-07-23, Marc Espie es...@nerim.net wrote: Nope, this exists elsewhere. Reuse bin/check-conflicts Speaking of which, here's what check-conflicts reports for the 2014-07-22 amd64 bulk build:

Re: Unmarked conflict checking in portcheck

2014-07-24 Thread Vadim Zhukov
2014-07-24 15:33 GMT+04:00 Christian Weisgerber na...@mips.inka.de: On 2014-07-23, Marc Espie es...@nerim.net wrote: Nope, this exists elsewhere. Reuse bin/check-conflicts Speaking of which, here's what check-conflicts reports for the 2014-07-22 amd64 bulk build:

Re: Unmarked conflict checking in portcheck

2014-07-24 Thread Vadim Zhukov
2014-07-24 15:33 GMT+04:00 Christian Weisgerber na...@mips.inka.de: Speaking of which, here's what check-conflicts reports for the 2014-07-22 amd64 bulk build: p5-TAP-Parser-0.54p0(devel/p5-TAP-Parser),p5-Test-Harness-3.30(devel/p5-Test-Harness)

Re: Unmarked conflict checking in portcheck

2014-07-24 Thread Andrew Fresh
On Thu, Jul 24, 2014 at 09:39:05PM +0400, Vadim Zhukov wrote: 2014-07-24 15:33 GMT+04:00 Christian Weisgerber na...@mips.inka.de: Speaking of which, here's what check-conflicts reports for the 2014-07-22 amd64 bulk build:

Re: Unmarked conflict checking in portcheck

2014-07-24 Thread Vadim Zhukov
2014-07-24 21:48 GMT+04:00 Andrew Fresh and...@afresh1.com: On Thu, Jul 24, 2014 at 09:39:05PM +0400, Vadim Zhukov wrote: 2014-07-24 15:33 GMT+04:00 Christian Weisgerber na...@mips.inka.de: Speaking of which, here's what check-conflicts reports for the 2014-07-22 amd64 bulk build:

Unmarked conflict checking in portcheck

2014-07-23 Thread Vadim Zhukov
Hello all. This adds a useful but awfully slow feature: checking for unmarked conflicts. This is done as a part of PLIST checks, so it could be disabled by -P as well as by specifically added -C option. Yes, there was -C option at some time previously with different meaning, but I'm doubt we care

Re: Unmarked conflict checking in portcheck

2014-07-23 Thread Marc Espie
On Thu, Jul 24, 2014 at 02:38:34AM +0400, Vadim Zhukov wrote: 2014-07-24 0:18 GMT+04:00 Vadim Zhukov persg...@gmail.com: Hello all. This adds a useful but awfully slow feature: checking for unmarked conflicts. This is done as a part of PLIST checks, so it could be disabled by -P as well

Re: Unmarked conflict checking in portcheck

2014-07-23 Thread Vadim Zhukov
2014-07-24 2:46 GMT+04:00 Marc Espie es...@nerim.net: On Thu, Jul 24, 2014 at 02:38:34AM +0400, Vadim Zhukov wrote: 2014-07-24 0:18 GMT+04:00 Vadim Zhukov persg...@gmail.com: Hello all. This adds a useful but awfully slow feature: checking for unmarked conflicts. This is done as a part

Re: Unmarked conflict checking in portcheck

2014-07-23 Thread Stuart Henderson
On 2014/07/24 00:46, Marc Espie wrote: Nope, this exists elsewhere. Reuse bin/check-conflicts This is different, unlke check-conflicts it doesn't need a full set of built packages, it just uses pkglocatedb instead.

Re: Unmarked conflict checking in portcheck

2014-07-23 Thread Vadim Zhukov
2014-07-24 3:30 GMT+04:00 Stuart Henderson st...@openbsd.org: On 2014/07/24 00:46, Marc Espie wrote: Nope, this exists elsewhere. Reuse bin/check-conflicts This is different, unlke check-conflicts it doesn't need a full set of built packages, it just uses pkglocatedb instead. check-conflicts

Re: Unmarked conflict checking in portcheck

2014-07-23 Thread Stuart Henderson
On 2014/07/24 03:36, Vadim Zhukov wrote: 2014-07-24 3:30 GMT+04:00 Stuart Henderson st...@openbsd.org: On 2014/07/24 00:46, Marc Espie wrote: Nope, this exists elsewhere. Reuse bin/check-conflicts This is different, unlke check-conflicts it doesn't need a full set of built packages, it