[Buildroot] Release tarballs location

[Buildroot] Release tarballs location

[Thomas Petazzoni]

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

Release tarballs location

[Thomas Petazzoni]

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

Release tarballs location

[Zdenek Kabelac]

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

Release tarballs location

[Alasdair G Kergon]

If a release was moved to 'old' it generally means it's not one I
recommend you run - a newer release is a better one to use.
In general, the versions left there are the ones that showed themselves 
to be more stable.

When I did this week's release and removed the previous release (it's
a memory corruption bug in it) I started thinking about what we could do to
document this a bit better.

Yes, I could put them all directly into 'old' to deal with this immediate
problem - good idea.

Alasdair

[Buildroot] Release tarballs location

[Robert Schwebel]

Hello,

On Wed, Dec 22, 2010 at 02:49:01PM +0100, Thomas Petazzoni wrote:
> 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 ?

I second Thomas' position - we have the same problem in PTXdist as well.

Robert
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

[Buildroot] Release tarballs location

[Robert Schwebel]

Hello,

On Wed, Dec 22, 2010 at 02:49:01PM +0100, Thomas Petazzoni wrote:
> 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 ?

I second Thomas' position - we have the same problem in PTXdist as well.

Robert
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

[Buildroot] Release tarballs location

[Alasdair G Kergon]

OK - I've renamed 'old' to 'releases', put everything in there,
symlinked 'old' to it, and from now on will put new releases
in there immediately.

The next scheduled release is next weekend - current release cycle
extended to 3 weeks due to the holidays.

Alasdair

[Buildroot] [lvm-devel] Release tarballs location

[Thomas Petazzoni]

Hello Alasdair,

On Tue, 4 Jan 2011 14:49:01 +0000
Alasdair G Kergon <agk@redhat.com> wrote:

> OK - I've renamed 'old' to 'releases', put everything in there,
> symlinked 'old' to it, and from now on will put new releases
> in there immediately.

Awesome, thanks!

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Release tarballs location

[Thomas Petazzoni]

Hello Alasdair,

On Tue, 4 Jan 2011 14:49:01 +0000
Alasdair G Kergon <agk@redhat.com> wrote:

> OK - I've renamed 'old' to 'releases', put everything in there,
> symlinked 'old' to it, and from now on will put new releases
> in there immediately.

Awesome, thanks!

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com