Date: Tue, 05 Jun 2012 14:29:58 +0300 From: Sulev-Madis Silber <madis555@hot.ee> To: Michael Scheidell <scheidell@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD Ports conflicts checker Message-ID: <4FCDEDB6.5060305@hot.ee> In-Reply-To: <4FCDE0FE.8000804@FreeBSD.org> References: <20120605092417.CD25111F824@ketas-laptop.mydomain> <4FCDE0FE.8000804@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, I admit that this short summary was little too big. Bigger than the another report that regularly ends up in ports@ Maybe big maintainer groups need different approach to this. And this needs more refinement. I let things settle for a while and tell few weeks later what is left. With more sanity and size checks, maybe. Refined form of conflicts. This report already contains useful stuff but it's hard to spot currently. On 2012-06-05 13:35, Michael Scheidell wrote: > > > On 6/5/12 3:00 AM, Sulev-Madis 'ketas' Silber wrote: >> HTML version of this report is here: http://ketas.si.pri.ee/ports-conflicts/ports@FreeBSD.org >> >> For port accessibility/kdeaccessibility suggesting new CONFLICTS jovie-[0-9]* kdeartwork-[0-9]* kmag-[0-9]* kmousetool-[0-9]* kmouth-[0-9]* because of overlapping files bin/kmag (also used by accessibility/kmag) ... skipped 1396 other ones > you opened several pr's. > > dumping this into ports@ is less than helpful. > > -- > Michael Scheidell, CTO >>*| * SECNAP Network Security Corporation > d: +1.561.948.2259 > w: http://people.freebsd.org/~scheidell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FCDEDB6.5060305>