On Fri, 2007-02-02 at 21:54 +0100, Marius Mauch wrote: > On Fri, 02 Feb 2007 20:25:55 +0100 > Tom Fredrik Blenning Klaussen <[EMAIL PROTECTED]> wrote: > > > On Fri, 2007-02-02 at 19:56 +0100, Marius Mauch wrote: > > > On Fri, 02 Feb 2007 19:29:06 +0100 > > > Tom Fredrik Blenning Klaussen <[EMAIL PROTECTED]> wrote: > > > > > > > On Fri, 2007-02-02 at 14:04 +0200, Petteri Räty wrote: > > > > > Tom Fredrik Blenning Klaussen wrote: > > > > A file that needs to be looked at fulfills the following demands. > > > > 1. Is a gentoo installed file, in particular is found > > > > within /var/db/pkg/*/*/CONTENTS > > > > 2. Is executable > > > > 3. Is not a link, it is assumed that a link goes to another file within > > > > the same packet. > > > > 4. Is not a directory > > > > > > > > Anything that fullfills those demands and is not handled within the > > > > program is a possible bug. > > > > > > So all executable files in a package are bugs? I hope I'm missing > > > something here ... > > > Maybe you could just post your script, code is sometimes better than > > > humans for explaining algorithms. > > > > Well, you're missing the part about not handled and possible bug. As I > > said, some of the file types are handled, and are known to be bugs, some > > are unhandled and are probably bugs. Among the filetypes I handle are > > gif files. I can not see any reason why gif files should be executable, > > can you? > > Ok, so you're looking for executable files that shouldn't be executables. > That's much easier to understand, all that "handling" stuff was a bit > confusing to me as you never listed your goal.
Sorry about that, I did list my goal in the first mail, but it wasn't my real question. My real question concerned how to mass file bugs. Anyway, my real goal is to find lacking dependencies in ebuilds. All the bugs I've discovered so far are discovered as a sideeffect of the main goal which as stated is to find dependency problems. -- Tom Fredrik Blenning Klaussen <[EMAIL PROTECTED]> -- gentoo-dev@gentoo.org mailing list