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.54) id 1FMVf6-0001Qy-6C for garchives@archives.gentoo.org; Thu, 23 Mar 2006 19:40:00 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k2NJcIsQ007211; Thu, 23 Mar 2006 19:38:18 GMT Received: from mach.qrypto.org (connectioncable-084.headoff.net [217.30.222.84] (may be forged)) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k2NJUr7f009972 for ; Thu, 23 Mar 2006 19:30:53 GMT Received: (qmail 17151 invoked from network); 23 Mar 2006 19:30:51 -0000 Received: from unknown (HELO ?192.168.0.2?) (gentoo@192.168.0.2) by 192.168.0.1 with ESMTPA; 23 Mar 2006 19:30:51 -0000 From: Rumen Yotov Organization: personal To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Official overlay support Date: Thu, 23 Mar 2006 21:30:36 +0200 User-Agent: KMail/1.9.1 References: <441F35B9.8000406@gentoo.org> <200603232020.37728.rumen@qrypto.org> <623652d50603231043s64c47ef3j@mail.gmail.com> In-Reply-To: <623652d50603231043s64c47ef3j@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="nextPart2400629.kyA3nrravC"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200603232130.45238.rumen@qrypto.org> X-Archives-Salt: 1d41a1a5-3012-4b1e-8ba3-8cfc0ae6241d X-Archives-Hash: ef3c609b30f5b70213244f0c382b8d74 --nextPart2400629.kyA3nrravC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 23 March 2006 20:43, Chris Bainbridge wrote: > On 23/03/06, Rumen Yotov wrote: > > Hi, > > Using a remote overlays is rather simple, just do "emerge layman". > > Read the einfo and then "man layman". > > It works flawlessly, just tested this with one remote overlay. > > Beside that "man layman" explains pretty much of it's innerwork. > > PS:There's an article in "gentoo-wiki.com" with a list of overlays. > > HTH.Rumen > > What is the status of those overlays? I believe the php, webapps, and > java ones (at least) are official (in that they're run by gentoo devs) > and bugs are to be reported to bugs.g.o, no? But the wiki page > http://gentoo-wiki.com/Portage_Overlay_Listing says "NEVER report bugs > at bugs.gentoo.org for these ebuilds." So where should users report > bugs? And how are they to know that? Hi, =46rom a very quick scan - yes there're some overlays made/supported by Gen= too=20 devs and some others are hosted/maintained by users,so i think for the latt= er=20 case you can't use Bugzilla in a sense that the ebuild is not in the tree. But looking from another angle (POV) if this is a new version ebuild or an= =20 ebuild for a new (not in the tree) package, why not report it's=20 status/workings/bugs in Bugzilla, generally it'll be an usefull info. Like now when somebody files a Bug on a new version or makes and attaches=20 initial ebuild for a new package. Of course all depends on the policy (if any is made) about this external=20 (official & unofficial) overlays and Bugzilla. PS: you can yourself see/read there're big differences in opinion even betw= een=20 Gentoo devs conserning overlays. So a bug-report assigned to a dev who=20 doesn't want to support overlays will probably get "WONTFIX" whatever. Rumen --nextPart2400629.kyA3nrravC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2-ecc0.1.6 (GNU/Linux) iD8DBQBEIvdlNbtuTtsWD3wRAm7iAJ9nGw7urIOKXzJciffLKhDgDnApCACdE8jy DOIwQTQsZo3VKEMDfiOgXso= =SiBY -----END PGP SIGNATURE----- --nextPart2400629.kyA3nrravC-- -- gentoo-dev@gentoo.org mailing list