From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Multiple versions of boost.
Date: Sat, 19 Mar 2016 10:33:07 +0100
Message-ID: <8737rm4xt8.fsf@mdc-berlin.de>
References: <87r3f6x21n.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52946)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Ricardo.Wurmus@mdc-berlin.de>) id 1ahDG4-0007E3-U2
	for guix-devel@gnu.org; Sat, 19 Mar 2016 05:33:21 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Ricardo.Wurmus@mdc-berlin.de>) id 1ahDG1-0001iv-OT
	for guix-devel@gnu.org; Sat, 19 Mar 2016 05:33:20 -0400
In-Reply-To: <87r3f6x21n.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org


Roel Janssen <roel@gnu.org> writes:

> I would like to add the older versions as packages as well, and my
> current approach is to inherit most of the 1.60.0 package:
>
> (define boost-1.57.0
>   (package (inherit boost)
>     (name "boost")
>     (version "1.57.0")
>     (source (origin
>               (method url-fetch)
>               (uri (string-append
>                     "mirror://sourceforge/boost/boost_"
>                     (string-map (lambda (x) (if (eq? x #\.) #\_ x)) ver=
sion)
>                     ".tar.bz2"))
>               (sha256
>                (base32
>                 "0rs94vdmg34bwwj23fllva6mhrml2i7mvmlb11zyrk1k5818q34i")=
)))))
>
>
> Is this a workable approach?  If not, how could I go about adding
> multiple versions?

In principle this should be enough, but having packaged older versions
of boost myself I know that it=E2=80=99s not enough in reality.  Previous
versions of boost often have different directory names, so patches and
substitutions in build phases in our new boost package don=E2=80=99t appl=
y
cleanly to older boost sources.  On Monday I could share one of my boost
variant packages.

> My other questions:
> - What is the convention with the Scheme variable name for the package?
> - Should I distinguish the package name in its version?

I don=E2=80=99t think there=E2=80=99s a convention.  Sometimes a differen=
t version is
needed for one package only, so we name it something like
=E2=80=9Cguile-for-guile-emacs=E2=80=9D or =E2=80=9Carmadillo-for-rcpparm=
adillo=E2=80=9D.  Then some
other times we just append a part of the version number to the variable
name.

~~ Ricardo