Comments on: Statistics on binary pkgsrc use

By: John Marino

John Marino — Mon, 29 Mar 2010 18:24:03 +0000

Ah, ok. Thanks for the link, I wasn’t aware of that nice report.

By: Anonymous

Anonymous — Sat, 27 Mar 2010 08:03:36 +0000

??????

By: Justin

Justin — Fri, 26 Mar 2010 23:01:22 +0000

John – the existing reports on avalon list the top “packages breaking other packages”, plus a full list of everything that didn’t work, plus links to the build logs to show what went wrong. For example:

http://avalon.dragonflybsd.org/reports/i386/2.4/20100320.0544/meta/report.html

By: Justin

Justin — Fri, 26 Mar 2010 22:59:24 +0000

I don’t see kicad in pkgsrc, and qucs is only available in the “wip” branch, which I’m not building since that’s a test area. I’m only building the current pkgsrc release branch at any given time, for a variety of reasons. If you can get those added as package to pkgsrc proper, they’ll be on avalon too.

By: faysal

faysal — Fri, 26 Mar 2010 15:14:03 +0000

may be i am posting an irrelevent topic but please add KICAD and QUCS in avalon repository.These are much important packages fall under CAD catagory.

By: John Marino

John Marino — Fri, 26 Mar 2010 14:01:18 +0000

I see now it’s the most requested packages, and includes packages that build fine. Is there any way to automate a report to tell us which ones on the long list are broken? Or have dependencies that are broken?

By: John Marino

John Marino — Fri, 26 Mar 2010 13:57:24 +0000

Hey great work, Justin!
This is a really interesting report. It looks like the most prudent approach is just start at the top of the list and start working down.

Is there a published procedure to provide patches/Makefile updates to the designee? If not, what’s the process to feed this back?