From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/1639 Path: news.gmane.org!not-for-mail From: idunham@lavabit.com Newsgroups: gmane.linux.lib.musl.general Subject: Re: Help-wanted tasks for musl Date: Sun, 19 Aug 2012 04:10:15 -0400 (EDT) Message-ID: <2063.50.0.229.183.1345363815.squirrel@lavabit.com> References: <20120819042611.GA8731@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1345363831 16227 80.91.229.3 (19 Aug 2012 08:10:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 19 Aug 2012 08:10:31 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-1640-gllmg-musl=m.gmane.org@lists.openwall.com Sun Aug 19 10:10:31 2012 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1T30ac-0005Rs-CK for gllmg-musl@plane.gmane.org; Sun, 19 Aug 2012 10:10:30 +0200 Original-Received: (qmail 30617 invoked by uid 550); 19 Aug 2012 08:10:28 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 30606 invoked from network); 19 Aug 2012 08:10:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lavabit; d=lavabit.com; b=spgQ0XvyXuhQRgxJXSLQ6RQ8Kdur75XJPh3MHTtUkr3zx7DONahprDxTz9wRJT3iMQZjeB9FVm7dZKEk8EBAp4k1hirjVGtQPy4dYbbuawEHcTsbVgxPTZkoy75PELlZdWqfsTLo6sVacRmEhme7O4gufGEQGaNb2eT3zvoasXM=; h=Message-ID:In-Reply-To:References:Date:Subject:From:To:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding; In-Reply-To: <20120819042611.GA8731@brightrain.aerifal.cx> User-Agent: SquirrelMail/1.4.13 Xref: news.gmane.org gmane.linux.lib.musl.general:1639 Archived-At: > Hi all, > Here are some tasks I could really use some help on, based on current > topics and requests that have come up on the list and IRC. Any > volunteers? See below... > Interfacing with a proxy/cache daemon using nscd protocol is one of > the proposed options for allowing musl to deal with NIS/LDAP/etc. user > databases. In order to evaluate the option, we need to know how the > protocol works and what's involved in making queries and receiv > Analysis of Gregor's pkgsrc failure results > > Gregor Richards has run the whole NetBSD pkgsrc build (over 10k > packages) against musl and posted reports to the mailing list and > wiki. Some analysis on the most frequent causes of failure could be > extremely helpful to improving compatibility. It would also be nice to > identify major dependency failures that can be fixed (either in the > upstream package if it's buggy, or in musl if it's due to missing > features) so that the packages which depend on them can be tested too. > I'm looking to get results in the form of "we should fix X and Y and Z > and then lots more packages will work". > ISTR that Gregor has something that gives him scores for how important different packages are. I look at this once in a while already, but now that I've done a little repartitioning, should be able to do a little more... Just for a brief overview of a few things: -SDL: patches haven't been merged -There are at least a dozen packages that should be building, per my own tests without pkgsrc, but aren't. -e2fsprogs provides libcomerr, so I suspect blocks zephyr, which blocks libpurple/pidgin/... -avahi is semi-important -ruby has been one of the higher-priority ones to fix -R needs g77 or gfortran a/k/a g95 (I have g77, but that's not in pkgsrc...). Also needs lapack & blas which need the same. Octave needs all of the above, plus more... I suspect that applying musl patches to gcc-core, and untarring gfortran on that, would be adequate-that's what I did for g77. -qt3 & qt4 libs won't build OOB. > Regression testing > > This is a big project, but there are lots of things that can be done > to contribute without doing it all. Basically it entails reading the > git log, identifying all bugs fixed, and for each bug, formulating a > test that reflects whether the bug exists or not. > Is git shortlog |grep -i bug going to be enough to catch them all, or not?