From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1I7NuF-0003sY-K6 for garchives@archives.gentoo.org; Sun, 08 Jul 2007 03:57:56 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l683uwF3000485; Sun, 8 Jul 2007 03:56:58 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l683sBDV029083 for ; Sun, 8 Jul 2007 03:54:11 GMT Received: from ip6-localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id A6B3265201 for ; Sun, 8 Jul 2007 03:54:09 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] automated extended information gathering Date: Sat, 7 Jul 2007 23:56:32 -0400 User-Agent: KMail/1.9.7 References: <200707071743.44605.vapier@gentoo.org> <200707072319.40004.vapier@gentoo.org> <8cd1ed20707072031n6d4e47c7l4ea616660c6dcefb@mail.gmail.com> In-Reply-To: <8cd1ed20707072031n6d4e47c7l4ea616660c6dcefb@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1662769.fHRnOzOEC5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200707072356.33088.vapier@gentoo.org> X-Archives-Salt: 5e882a12-cc4d-4831-b9c9-07c8e4131b13 X-Archives-Hash: 2543a0e8a689417c1a1040fd9d44c689 --nextPart1662769.fHRnOzOEC5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 07 July 2007, Kent Fredric wrote: > On 7/8/07, Mike Frysinger wrote: > > On Saturday 07 July 2007, Kent Fredric wrote: > > > Implementation details wise, I would like to see packages have > > > possibly 2 functions, > > > 1: Info, and 2: Check. > > > Reason Being that you wont be able to fetch installation status info > > > on a package thats not installed, and if a package is failing to > > > install, you're more likely wanting to check the status of the things > > > it depends on, not the package itself. > > > > i dont really understand what you're going for here ... the point was to > > get extended information on things that are installed ... i dont know > > what you'd want/expect for trying to query packages that arent installed > > > > > Check would contain manual tests for a given package, thats either > > > installed or not installed ,as well as names of packages to run info > > > on. > > > > > > Info would be more usefull in diagnosing mis-installed packages or > > > packages that failed to run properly despite being compiled and > > > installed without a hitch ( it happens ) > > > > sounds like you're duplicating the point of src_test() but without any > > real way of quantifying it or making it useful to coordinate things ... > > please expound on what you're going for because i'm just not seeing it > > ... > > 50% of bugs I tend to see are compile failures. > > Compile Failures are often a result of things that the compile was > dependant on. > > Thus, finding info on a given package to understand what its problem > is, you should be info-querying its dependants, not the package > itself, no? > > Information you want sent to bug reports are related to the software > that it depended on, no? ( ie: xine-libs wont compile : emerge --info > xine-libs should report information on ffmpeg, which has changed, > causing the failure ) > > And if xine libs wasnt installed, it would be pointless to report > information about xine-libs installation when its not installed > becasue it cant be ;) > > So instead of asking the user what version of X dependant they have, > emerge --info atom should report that in a standardised way, making > them able to provide more relevant information in the initial report so you're asking for `emerge --info ` to walk the dependency tree and= =20 include --info for all things that depends on ? how is this relevan= t=20 to the check() function you proposed ? you are trying to install package X which depends on package Y which is=20 broken ... i dont think it's possible/feasible to have ebuilds try and=20 diagnosis itself automatically to figure out *how* exactly package Y is=20 broken ... if it were possible, we'd be able to write self-healing ebuilds =2Dmike --nextPart1662769.fHRnOzOEC5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (GNU/Linux) iQIVAwUARpBgcEFjO5/oN/WBAQKxtBAApUWOgsOE3s9miJUTJ7V/1cMOQ00yoWku nSHf7jn1oC+ekTMAjwfuRxFpjO7rFIDBa5eYc6UfNSvXqtLvbiG5PIa19gfymhb/ AW0/PCB4jAEJJUZlvXG72IfFeSvuMYT4tRkKdFLjhI0UXn379b9hlC1xWprlSLiw X3vkmyh16HF8va60+sz1t597zLXjbIJkUzMg08iS8gRGA+rnyfquPXKTiA3eMaqc HlDUE27Q/nXaiSgXb1tyWapHjasb6Uj4zYBZNhV6a5T8FKKH6keLpFINBu4guSc4 tzVlvfFp35wEZE1KPnABEPC6n07ApOxaRvJgz2X654uogb6ARf9uFCXJCtXgXmoa xu4w2MOBlegywdFT2EwxN9sPyRmXvV0d+hP6zi4dWQu/BMPIpo2AhmqV+ur6mcix Iwl25ZSHh4VNvkDkrYVyviMXl7b1SJkv9lIsSS01f5CEJHvlCg/2eDeuL/PelkCN OcrrbT+21t7k8KMxyv+IGQysCSB6vdDI0IXxp3TfaLGiSOVwvCesUA/8Ai2sRvWV arNGOALfCKUxmbtSgZX+MyZhh+4UA9XJZppctwNiUtFI3u6PEAx0xDm3Mye4umUY AaiAbVuz2tkWEE2AHhRHpgM6um5o+Tapxb046Tb+gp/n70pSJnM0gQFlNTQ52MjD xkBFVMFaJjE= =0wf6 -----END PGP SIGNATURE----- --nextPart1662769.fHRnOzOEC5-- -- gentoo-dev@gentoo.org mailing list