Return-Path: X-Original-To: apmail-mesos-user-archive@www.apache.org Delivered-To: apmail-mesos-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB2191778C for ; Mon, 21 Sep 2015 20:01:02 +0000 (UTC) Received: (qmail 2425 invoked by uid 500); 21 Sep 2015 20:00:59 -0000 Delivered-To: apmail-mesos-user-archive@mesos.apache.org Received: (qmail 2362 invoked by uid 500); 21 Sep 2015 20:00:59 -0000 Mailing-List: contact user-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@mesos.apache.org Delivered-To: mailing list user@mesos.apache.org Received: (qmail 2352 invoked by uid 99); 21 Sep 2015 20:00:59 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Sep 2015 20:00:59 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 16450C0AB3 for ; Mon, 21 Sep 2015 20:00:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.199 X-Spam-Level: ** X-Spam-Status: No, score=2.199 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id JGKdxBjTiFA0 for ; Mon, 21 Sep 2015 20:00:52 +0000 (UTC) Received: from mail-qg0-f46.google.com (mail-qg0-f46.google.com [209.85.192.46]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 005F142B78 for ; Mon, 21 Sep 2015 20:00:41 +0000 (UTC) Received: by qgx61 with SMTP id 61so99496468qgx.3 for ; Mon, 21 Sep 2015 13:00:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FmF9V0FF8L0k2gDG4ZgVttOVoAqeqZglTBQbXhg3eBc=; b=ShuehSHRKVVt+L28xHDUvVAM5vUts7tfprtQ9pnMfNIBfUD5YTjDetQtxf3WEiXTiW emFgRG2JD7SNQRVIYQG5aXgm8omjMN9HkWDcPl/F/Z6rT7iVQuyxXBo0DKr1uMDVXmVs GQRXvLsNOtmFqJEOM3+py0tTE+F3+5PE03ZHFGCd5f11w/mvsVRuYZIKlNV42gyHHRnj CaggQbdpmPeQp2Ui/Y0M1DzHameRFJKzoX0i5O4KmjwBESCZkfRKd1Ehjtkk3sldJDgL +p8XpOQ2jfgLuAyqCzqUxYLBt2FYjuPkQbck8mFA1jcIajoEseUy+uukTq+Gu7a452VJ SSBA== X-Received: by 10.141.23.210 with SMTP id z201mr25183730qhd.104.1442865640696; Mon, 21 Sep 2015 13:00:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.29.196 with HTTP; Mon, 21 Sep 2015 13:00:21 -0700 (PDT) In-Reply-To: References: <55FCB593.1080409@tampabay.rr.com> <55FCE7C0.1080006@tampabay.rr.com> From: craig w Date: Mon, 21 Sep 2015 16:00:21 -0400 Message-ID: Subject: Re: mesos 0.24 released? To: user@mesos.apache.org Cc: ccaat@tampabay.rr.com Content-Type: multipart/alternative; boundary=001a11423610f8f3eb05204755dc --001a11423610f8f3eb05204755dc Content-Type: text/plain; charset=UTF-8 Thanks for following up. On Mon, Sep 21, 2015 at 3:00 PM, Vinod Kone wrote: > Published the blogpost for 24.0. > > On Fri, Sep 18, 2015 at 9:42 PM, CCAAT wrote: > >> >> Oh, >> >> Here is a link that explains the Variable meanings for the packages >> downloaded by gentoo's package manager, portage:: >> >> https://devmanual.gentoo.org/ebuild-writing/variables/ >> >> I really am at the stage that I want/need to test many tarball releases >> and also to start testing on other architectures, like aarch64. >> Please advise on the location(s) of these tarballs, even if they >> are not formal releases or release candidates. >> >> Is anyone testing tarball compilations on other arches? >> Do I need to start reading the dev list for this sort of granularity? >> All suggestions are most welcome >> >> >> curiously, >> James >> >> >> >> >> >> I'm confused. Here at gentoo, we usually (almost always) follow the >>> release numbers including the full minor release number designations >>> of the tarball. So if I download a tarball, it's not references by minor >>> release number? >>> >>> Here is a simple, quick example:: >>> >>> www-client/seamonkey Available versions: 2.33.1-r1 2.35 >>> >>> This accuracy is quintessentially necessary for the gentoo community. >>> Do I have to fix the name of the tarballs manually? In gentoo ebuilds, >>> the files that download, the tarballs directly from a source repo >>> the exact and complete version number is necessary. Should >>> I use github? >>> >>> What are recommendations for this? >>> >>> Here is what I'm using for mesos' current ebuild:: >>> >>> SRC_URI="http://apache.org/dist/${PN}/${PV}/${P}.tar.gz" >>> >>> >>> curiously, >>> James >>> >>> >>> >>> >> > -- https://github.com/mindscratch https://www.google.com/+CraigWickesser https://twitter.com/mind_scratch https://twitter.com/craig_links --001a11423610f8f3eb05204755dc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks for following up.
<= br>
On Mon, Sep 21, 2015 at 3:00 PM, Vinod Kone <= span dir=3D"ltr"><vinodkone@apache.org> wrote:
Published the blogpost for 24.0.

On Fri, Sep 18, 2015 at 9:42 PM= , CCAAT <ccaat@tampabay.rr.com> wrote:

Oh,

Here is a link that explains the Variable meanings for the packages
downloaded by gentoo's package manager, portage::

https://devmanual.gentoo.org/ebuild-writing/va= riables/

I really am at the stage that I want/need to test many tarball releases
and also to start testing on other architectures, like aarch64.
Please advise on the location(s) of these tarballs, even if they
are not formal releases or release candidates.

Is anyone testing tarball compilations on other arches?
Do I need to start reading the dev list for this sort of granularity?
All suggestions are most welcome


curiously,
James





I'm confused. Here at gentoo, we usually (almost always) follow the
release numbers including the full minor release number designations
of the tarball. So if I download a tarball, it's not references by mino= r
release number?

Here is a simple, quick example::

www-client/seamonkey=C2=A0 =C2=A0 =C2=A0 =C2=A0 Available versions:=C2=A0 2= .33.1-r1 2.35

This accuracy is quintessentially necessary for the gentoo community.
Do I have to fix the name of the tarballs manually?=C2=A0 In gentoo ebuilds= ,
the files that download, the tarballs directly from a source repo
the exact and complete version number is necessary.=C2=A0 =C2=A0Should
I use github?

What are recommendations for this?

Here is what I'm using for mesos' current ebuild::

SRC_URI=3D"http://apache.org/dist/${P= N}/${PV}/${P}.tar.gz"


curiously,
James








--
--001a11423610f8f3eb05204755dc--