From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: Release tarballs location
Date: Wed, 22 Dec 2010 15:53:34 +0100 [thread overview]
Message-ID: <4D1210EE.4020406@redhat.com> (raw)
In-Reply-To: <20101222144901.5d2bb8c7@surf>
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
next prev parent reply other threads:[~2010-12-22 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 13:49 [Buildroot] Release tarballs location Thomas Petazzoni
2010-12-22 13:49 ` Thomas Petazzoni
2010-12-22 14:53 ` Zdenek Kabelac [this message]
2010-12-22 15:06 ` Alasdair G Kergon
2010-12-23 10:04 ` [Buildroot] " Robert Schwebel
2010-12-23 10:04 ` Robert Schwebel
2011-01-04 14:49 ` Alasdair G Kergon
2011-01-04 15:02 ` [Buildroot] [lvm-devel] " Thomas Petazzoni
2011-01-04 15:02 ` [Buildroot] " Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D1210EE.4020406@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.