<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/17/2014 01:23 PM, Jim Kinney
wrote:<br>
</div>
<blockquote
cite="mid:CAEo=5PzZVXwa4R5y3CGgX7wODK12VoDyc3dSSH26F3OudDz=dg@mail.gmail.com"
type="cite">
<div>There is no torrent available for the download. They use
reposync. Once the initial repo pull is done it's like rsync,
tiny.<br>
</div>
</blockquote>
<br>
I know that. I was talking about <i>creating</i> one, for the RC
repo they have online.<br>
<br>
<blockquote
cite="mid:CAEo=5PzZVXwa4R5y3CGgX7wODK12VoDyc3dSSH26F3OudDz=dg@mail.gmail.com"
type="cite">
<div>By using reposync, it'll setup your repodata correctly.</div>
</blockquote>
<br>
Yes, but they're not <i>updating</i> the repo. Right now, they're
publishing a whole-new-repo for every "build" of the nightly CentOS
system. They are not gpg signing, and because they're whole-system,
forced rebuilds, the BuildID embedded in every ELF will change,
meaning every RPM will be different. Meaning that the repo database
will show that all packages have changed and... reposync isn't any
better than wget is at this point. :-)<br>
<br>
My thinking was, other people might want to play with the
prereleases. I'm doing so because I simply mirrored the 6.5 GB repo
and am using that to install it on several systems in testing setups
at the moment. (It works rather nicely.) I figure I can't be the
only one to want that, and since there is only a single point to
mirror from, I thought it'd be nice to establish a mirroring
infrastructure for the RCs.<br>
<br>
CentOS won't fan-out to mirrors until they are far more ready than
they are now. I'd figure at least a couple weeks.<br>
<br>
— Mike<br>
</body>
</html>