From mboxrd@z Thu Jan  1 00:00:00 1970
From: Zdenek Kabelac <zkabelac@redhat.com>
Date: Wed, 22 Dec 2010 15:53:34 +0100
Subject: Release tarballs location
In-Reply-To: <20101222144901.5d2bb8c7@surf>
References: <20101222144901.5d2bb8c7@surf>
Message-ID: <4D1210EE.4020406@redhat.com>
List-Id: <lvm-devel.redhat.com>
To: lvm-devel@redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dne 22.12.2010 14:49, Thomas Petazzoni napsal(a):
> Hello,
> 
> I am a contributor of Buildroot, a tool that allows to easily build
> embedded Linux systems. We create recipes to cross-compile software
> that are useful on embedded systems, and LVM2 is one of them.
> 
> Unfortunately, it looks like when a release is made, the tarball is
> placed at ftp://sources.redhat.com/pub/lvm2/, but as once as a newer
> release is made, the previous tarball is moved into
> ftp://sources.redhat.com/pub/lvm2/old/. Unfortunately, this doesn't
> work well with how embedded Linux build systems work, since they code
> an URL and a version for each software they build. This is usually not
> a problem, since most of the software tarballs are available from a
> fixed location.
> 
> Would it be possible to change the release tarball location policy in
> order not to move them ? If you really want to have only the latest one
> in ftp://sources.redhat.com/pub/lvm2/, could you also put the latest
> available version in ftp://sources.redhat.com/pub/lvm2/old/ at the
> moment of the release ?
> 

Looks fairly simpler to implement support for mutliple links addresses
into the Buildroot?
(i.e. if the first location no longer exists try next one in the list)

Zdenek