Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84E3AEA57 for ; Thu, 29 Nov 2012 17:55:15 +0000 (UTC) Received: (qmail 7573 invoked by uid 500); 29 Nov 2012 17:55:15 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 7546 invoked by uid 500); 29 Nov 2012 17:55:15 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 7538 invoked by uid 99); 29 Nov 2012 17:55:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Nov 2012 17:55:15 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of thejaka.amila@gmail.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qc0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Nov 2012 17:55:07 +0000 Received: by mail-qc0-f179.google.com with SMTP id b14so10402729qcs.38 for ; Thu, 29 Nov 2012 09:54:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=hLy3U2qojS/aliamRMsIH3VOo8m9F9mi5z4BU+D5w94=; b=xqHrkr3DdxxHJDgoLASGSdRLGFF+Z/PBr6/gnlY5u3vk7ArSJIdwyRVzR6xaStPKlX jyshqO/0RclasD6Oc23rGXphw8NLuzOpU/k5UYTyVFXD6anBLMWnzMAGj6/GlxX0I8rf hIYi1NK/zNADqM3Wjk1+5uxK1Dq+wTARatnpoAWTxA85GCCC42Ow/98mmVTS2NWTtaYp pmHrAA3oRK2NFo/IvqgvfkgLsNBNNgaB85qsMypktA6SsqFctwFfttyee3l79wUhfFI0 iHqLv/OvRn8hA8Axr1k7PxjdtQFbVlYnh9+DWxdly97yIJvciPvkT1hdb9F7VrY/Y1+q 5pEw== MIME-Version: 1.0 Received: by 10.224.179.212 with SMTP id br20mr26428830qab.51.1354211686860; Thu, 29 Nov 2012 09:54:46 -0800 (PST) Received: by 10.49.132.102 with HTTP; Thu, 29 Nov 2012 09:54:46 -0800 (PST) In-Reply-To: References: Date: Thu, 29 Nov 2012 12:54:46 -0500 Message-ID: Subject: Re: Separation out Server & Client binary distributions in Airavata From: Amila Jayasekara To: dev@airavata.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I am working on changing distribution. I will work on this. Thanks Amila On Thu, Nov 29, 2012 at 12:25 PM, Lahiru Gunathilake wrote: > I am +1 for this and this is very clean and ideally nobody is going to use > airavata pack right away so providing these in separate would make life > easier for users to use three component separately. > > Thanks Saminda for bringing this up. > > Lahiru > > On Thu, Nov 29, 2012 at 12:22 PM, Saminda Wijeratne wrote: > >> Hi Devs, >> >> Currently we have both XBaya & the Airavata services bundled together when >> we create the final distribution. This can arise confusion to the users & >> unnecessary overhead of retrieving/understanding/configuring for different >> stakeholders. Shall we have different distributions as follows? >> >> >> 1. Airavata server binary distribution - everything related to hosting >> an Airavata Server >> 2. XBaya binary distribution - everything needed for XBaya >> to run independently >> 3. Airavata client binary distribution - all the libraries required >> for a 3rd party client to use the Airavata API >> >> >> (This would mean that we'll have 3 binary packs for an Airavata release) >> >> Regards, >> Saminda >> > > > > -- > System Analyst Programmer > PTI Lab > Indiana University