Benjamin Reed wrote: > Robert T Wyatt wrote: >> Build/installation statistics. > > Variations of this have been on my todo list for a while. > > I want to provide build pass/fail statistics auto-uploaded when > building, but also providing hooks to report usage would be nice too, > although more annoyingly invasive (and difficult to implement without > wrapping all binaries...)
Cool! I think the simplest implementation would be to send a successful build or install message to the maintainer so at least *they* would know that the package is working (and for how many people); unfortunately this may be too burdensome for our volunteer maintainers. Perhaps a dedicated recipient address could be used to store/sort/extract the data.... I think transmitting the user's architecture/environment would be an important part. (I guess spam and false reports would have to be filtered....) Even something as crude as sending the info to [EMAIL PROTECTED] could be useful if the package, version, and tree were in the subject. It is intended to help in the area of moving things from unstable to stable which is clearly a goal of the project. </preaching to the choir> ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
