From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23225 invoked by uid 1002); 5 Dec 2003 11:09:53 -0600 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 21261 invoked from network); 5 Dec 2003 11:09:53 -0600 Date: Fri, 5 Dec 2003 18:09:34 +0100 From: Marius Mauch To: gentoo-portage-dev@gentoo.org Cc: gentoo-dev@gentoo.org Message-Id: <20031205180934.75027506.genone@gentoo.org> Organization: Gentoo Linux X-Mailer: Sylpheed version 0.9.7claws (GTK+ 1.2.10; i686-pc-linux-gnu) X-Face: H@&[wkk?l:Zx:8i_5bViK&{Vz{c{~r),^&:v/r#+X5dmfA6qCl)~'Ul{"&06Q1[05.%v&c>je5R{=xLnx^=~lN~rO0xuR~~NY)CX\"Nc4$9CBPwDl-.pYuVeGdir86L@\:j?7@%Ej2?Wi-Y0=1]T14ce0w79Bckk[*ti{;iA"{;I}&E~.msRBsBS)N!CS4Gd|_UR Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Fri__5_Dec_2003_18_09_34_+0100_nhUsUHrC6ZX6hXcY" X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:7e6c91d1b14dbccceb2f2166522fa0f6 Subject: [gentoo-portage-dev] Portage-NG implementation language(s) X-Archives-Salt: 8686f310-b86a-409a-8c14-27e131f399a7 X-Archives-Hash: 30c5e54cb44c897390633f621e1b4f46 --Signature=_Fri__5_Dec_2003_18_09_34_+0100_nhUsUHrC6ZX6hXcY Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Hi, Seeing this "language war" on -dev I think I should say again that the component model should make us free from language restrictions. There is no sense in saying "we should use language XXX for portage-ng" as the goal should be that each component can be implemented in the best fitting language. So it should be possible to have the dependency resolver in prolog, the ebuild parser in perl, the frontend in python, the storage backend in C and so on. Instead of arguing about the "best" language for implementation we should discuss about the language for the _interface_ for the component interaction. Once we have decided on that we can start creating the global architecture that describes which components interact with each other, which components are mandatory or optional and so on. Later in that process we can specify the first function signatures and start implementing the individual components. Then and not earlier we have to choose the implementation language. I hope we can stop the "let's use XXX" discussion now. Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better. --Signature=_Fri__5_Dec_2003_18_09_34_+0100_nhUsUHrC6ZX6hXcY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/0LvSWzrL1pM7SNcRAtXGAJ9fFzaRSdyTg17lWAXGH7bEyY0jPACfV95o EnckStmUSy/GjHzAtGcYHmA= =KCGx -----END PGP SIGNATURE----- --Signature=_Fri__5_Dec_2003_18_09_34_+0100_nhUsUHrC6ZX6hXcY--