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.43) id 1E8Won-0007ee-AD for garchives@archives.gentoo.org; Fri, 26 Aug 2005 05:31:57 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7Q5UFms006210; Fri, 26 Aug 2005 05:30:15 GMT Received: from hermes.orakel.ods.org (dsl67-66.fastxdsl.nl [62.251.66.67]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7Q5UEtW009201 for ; Fri, 26 Aug 2005 05:30:14 GMT Received: from aphrodite.orakel.ods.org ([172.17.2.15]) by hermes.orakel.ods.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.50) id 1E8WoQ-0000Ma-Av for gentoo-osx@lists.gentoo.org; Fri, 26 Aug 2005 07:31:34 +0200 Message-ID: <430EA934.2070505@gentoo.org> Date: Fri, 26 Aug 2005 07:31:32 +0200 From: Grobian Organization: Gentoo Foundation User-Agent: Thunderbird 1.0+ (Macintosh/20050813) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-osx@gentoo.org Reply-to: gentoo-osx@lists.gentoo.org MIME-Version: 1.0 To: gentoo-osx@lists.gentoo.org Subject: Re: [gentoo-osx] Re: Documentation Update References: <3D149028-DB30-4FA8-AD2B-D26794C40101@gentoo.org> <43963.192.16.196.142.1123833555.squirrel@webmail.orakel.ods.org> <7A90CF45-1722-4DEE-AE2F-FF06F5B91D97@gentoo.org> <43086F5C.1060903@gentoo.org> <683502A8-2391-4B17-9B3F-A1F427C5FAEF@gentoo.org> <50407.192.16.196.142.1124955381.squirrel@webmail.orakel.ods.org> <219A9CD1-A9AD-4B8F-A0F3-15DA2FB50FB4@iinet.net.au> In-Reply-To: <219A9CD1-A9AD-4B8F-A0F3-15DA2FB50FB4@iinet.net.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Scanned: by hermes.orakel.ods.org (Exim Exiscan) using SpamAssassin and ClamAV X-Archives-Salt: d15d476d-26ea-427e-87ef-46b97282555f X-Archives-Hash: 6ded5892609fe40e84c65f3b2dbfbb7e Mike Z. wrote: > Definitely, compilation is fine, but you need to have some sort of > runtime testing as well. On the note of libraries, I would think, rather > than keywording libraries that compile, we should wait until an > application that requires them also needs to be keyworded. This will > probably depend on which library it is, but it'd mean that we have a > full deptree for each application, as well as a useful real-world test > case. This is in general the case. We cannot keyword a library without having it tested. My keyword for mp (the editor) was an example of this, I needed something small to test libpcre. I think when people report a library working/compiling, they use the library in some application. Maybe that application is not in portage, or so big that it isn't an appropriate test case, but I'd still like to keyword (unstable) libraries before a separate bug for an application using the library is there, because it's enormously annoying to have to keyword a whole tree of dependencies to figure out the 6th level dependency does not and will never compile. -- Fabian Groffen Gentoo for Mac OS X -- gentoo-osx@gentoo.org mailing list