[Nix-dev] Stablilizing stdenv-updates

[Michael Raskin]

<871uv0obtn.fsf at write-only.cryp.to> <87d3eg1jm1.fsf at gnu.org>
<E1RATgP-0005Vd-00.7c6f434c-mail-ru at smtp1.mail.ru>
<20111002215413.GU1976 at vicerveza.homeunix.net>
<87zkhjuk7i.fsf at write-only.cryp.to>
<20111002221223.GW1976 at vicerveza.homeunix.net>
<87k48nrn2f.fsf at gnu.org> <87pqiev0ut.fsf at write-only.cryp.to>
<87sjnam4xb.fsf_-_ at gnu.org>)
Mime-Version: 1.0
Content-type: text/plain; charset="UTF-8"

> 
>> For instance, gnupdate turned up a glibc update (2.14), which I didn’t
>> commit because the glibc-ports package isn’t available yet.  I’d be
>> tempted to wait until it’s available, and at that point update to 2.14
>> and see what happens.
>googling "glibc-2.14" gives 
>http://pkgs.fedoraproject.org/repo/pkgs/glibc/glibc-
>ports-2.14.tar.xz/05c85905b43021a81318c3aa81718019/
>
>How is it related to http://ftp.gnu.org/gnu/glibc/ ?

Searching 2.14 on ftp.gnu.org gives glibc-2.14

How is Google doing the almost-right-but-not-quite (as usual) thing 
relevant?