From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5697 invoked by uid 1002); 4 Oct 2003 18:27:38 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 6108 invoked from network); 4 Oct 2003 18:27:38 -0000 Date: Sat, 4 Oct 2003 20:27:23 +0200 From: Patrick =?ISO-8859-1?Q?B=F6rjesson?= To: gentoo-dev@gentoo.org Message-Id: <20031004202723.65d7ee16.psycho@rift.ath.cx> In-Reply-To: <200310041729.52354.luke-jr@gentoo.org> References: <3F7D4315.1020900@gentoo.org> <200310041436.43568.luke-jr@gentoo.org> <20031004175629.09f342a0.psycho@rift.ath.cx> <200310041729.52354.luke-jr@gentoo.org> Organization: HiS X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Sat__4_Oct_2003_20_27_23_+0200_KmCA_1fCx.Ffy2j=" Subject: Re: [gentoo-dev] Speaking of new kernels being added to the tree X-Archives-Salt: 13da481d-fa62-40ff-b090-d09ccaba7ba6 X-Archives-Hash: ca25f478838093036a6db23a31981216 --Signature=_Sat__4_Oct_2003_20_27_23_+0200_KmCA_1fCx.Ffy2j= Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > In theory, Portage could track them if ebuild could be modified to use > /usr/src/pkg when it existed instead of /var/tmp/portage/*/work and > the application was installed via 'ebuild pkg merge'. I'm not sure how > possible that would be for implementation, though. But then the question is: Why? We already have the source unpacked in /var/tmp/portage/*/work so why "move" it to /usr/src? There are already ways for people to do the configure- and make-steps them selves if they wish (through the ebuild-command as you yourself said). As I see it there would be no advantage reimplementing it the proposed way... As for the kernels to be auto-configured, why not do it the same way as some other packages do it: have an extra section in the ebuild that configures the kernel for you through genkernel... Several other packages already have this section (think it's called config) including postresql. This could be advertised in the same way as in the postresql-ebuild at the end of the emerge-command, and thus everybody has a choice in how they would like to configure and compile the kernel. Patrick B=F6rjesson --=20 Public key id: 4C5AB0BF Public key available at search.keyserver.net[:11371] --Signature=_Sat__4_Oct_2003_20_27_23_+0200_KmCA_1fCx.Ffy2j= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/fxEOoil/ZExasL8RAgWQAJ9gC104UA4vbX8fIKPd7t2YI2W44gCeILy0 I9GGovtEVDBsizuHXghLmoM= =/EWk -----END PGP SIGNATURE----- --Signature=_Sat__4_Oct_2003_20_27_23_+0200_KmCA_1fCx.Ffy2j=--