linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: kernel.org udev tarballs
Date: Fri, 04 Nov 2011 10:01:00 +0000	[thread overview]
Message-ID: <20111104100100.GB20768@pengutronix.de> (raw)
In-Reply-To: <7a04ec9f-f4d4-4214-b408-8419ed2125d1@zose-store-12>

On Thu, Nov 03, 2011 at 05:09:32AM -0700, Greg KH wrote:
> On Thu, Nov 03, 2011 at 11:00:40AM +0100, Michael Olbrich wrote:
> > On Wed, Nov 02, 2011 at 03:46:26PM +0100, Kay Sievers wrote:
> > > 2011/11/2 Greg KH <greg@kroah.com>:
> > > > On Wed, Nov 02, 2011 at 03:05:52PM +0100, Benoît THÉBAUDEAU wrote:
> > > >> Does anyone know if the udev tarballs will be put back on
> > > >> http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev/
> > > 
> > > The current release is just here:
> > >   http://people.freedesktop.org/~kay/
> > > 
> > > >> or should we rely only on git snapshots from now on?
> > > 
> > > You can always just check out a git tag and do:
> > >   ./autogen
> > >   make
> > >   make distcheck
> > > to get any tarball you need.
> > > 
> > > > They will be put back there, please give us time.
> > > 
> > > Not sure if all the old release tarballs will ever come back to kernel
> > > org. Git is the better archive for that anyway.
> > > 
> > > The new releases will be there for sure when the infrastructure is
> > > ready. In the meantime, you can just get old releases from any of the
> > > distros archives who stored them in their build systems with proper
> > > checksums.
> > 
> > That really depends on the use-case. All embedded Linux distributions that
> > I know of rely on upstream to provide the tarballs.
> 
> Why do they do this?  If they are expecting that upstream's tarballs
> will always be there to abide by the GPL, then they might wish to
> reconsider that :)

There are no binaries here. It's just rules how to build things. With
downloading the tarball as a first step.

> > And the big distributions only keep the versions they actually use and that
> > changes all the time.
> > So please upload the old tarballs again, once the infrastructure is ready.
> 
> You can always create the old tarball yourself automatically from git if
> needed.

Really? Different versions for autoconf/automake/libtool etc. introduce an
amount of uncertainty I'm not really comfortable with.

Michael

-- 
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 |

      parent reply	other threads:[~2011-11-04 10:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 14:05 kernel.org udev tarballs 
2011-11-02 14:35 ` Greg KH
2011-11-02 14:46 ` Kay Sievers
2011-11-03 10:00 ` Michael Olbrich
2011-11-03 12:09 ` Greg KH
2011-11-03 13:08 ` Kay Sievers
2011-11-04 10:01 ` Michael Olbrich [this message]

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=20111104100100.GB20768@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=linux-hotplug@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).