From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Release tarballs location
Date: Wed, 22 Dec 2010 14:49:01 +0100 [thread overview]
Message-ID: <20101222144901.5d2bb8c7@surf> (raw)
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 ?
Thank you very much!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2010-12-22 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 13:49 Thomas Petazzoni [this message]
2010-12-23 10:04 ` [Buildroot] Release tarballs location Robert Schwebel
[not found] ` <20110104144901.GE13802@agk-dp.fab.redhat.com>
2011-01-04 15:02 ` [Buildroot] [lvm-devel] " 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=20101222144901.5d2bb8c7@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox