From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 233 invoked by uid 1002); 5 Dec 2003 18:41:54 -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 20468 invoked from network); 5 Dec 2003 18:41:54 -0600 X-WM-Posted-At: mailandnews.com; Fri, 5 Dec 03 19:41:53 -0500 From: Jason Stubbs To: gentoo-portage-dev@gentoo.org Date: Sat, 6 Dec 2003 09:41:42 +0900 User-Agent: KMail/1.5.93 References: <20031205180934.75027506.genone@gentoo.org> In-Reply-To: <20031205180934.75027506.genone@gentoo.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Message-Id: <200312060941.43134.jasonbstubbs@mailandnews.com> Subject: Re: [gentoo-portage-dev] Portage-NG implementation language(s) X-Archives-Salt: 7b6c302b-5b29-4db0-9094-c796bb608584 X-Archives-Hash: 2ba101fd8bee2ce703fc876a32351d71 On Saturday 06 December 2003 02:09, Marius Mauch wrote: > 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. I believe this is already part of the requirements. > 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. I think the point is that even designing the global architecture should come before deciding on a language for the component interaction interface. > 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. This is correct. The implementation language for a particular component will be chosen once the framework is decided and it is time to create said particular component within that framework. Regards, Jason Stubbs -- gentoo-portage-dev@gentoo.org mailing list