Wiki source for MageiaMirrors

Show raw source

Well a mirror is usually where you find repositories for RPM or ISO, there's a whole infrastructure behing mirrors in fact

===What are mirrors used for in Mageia and which parameters are important?===
~- rpm
~- ISO
~- size
~- audience: who? how many? (determines number of hits)
~- frequency of update
~- protocols used for end-user
~- svn / git (or any other [[ VCS]]) is not mirrorred
~- structure (directories, available bandwith, protocols...)

This is currently work in progress:
{{image class="center" alt="Mirrors mind map" title="Mirrors mind map" url="" link=""}}
Source is available at [[ MageiaMirrors.xmind]] (under this WikiLicense) see CompileXMind to edit it :)
~- add relations
~- precise directory structures
~- precise volumetry

===Related topics===
See for list of existing mirrors (and register), see source code at (license? AGPL3+?)
Documentation available at

See MandrivaMirrors for structure and size of mirrors

Check bittorrent limits (lack of duration in the long term, use of network not respecting topology...), there was an article by Red Hat or Fedora

Compatibility with MirrorBrain is a Download Redirector and generates Metalinks, Torrents and crypto-hashes [es] to determine dependencies to be installed (based on a ##rpm -qa##) in order to download them at a cybercafé (for example) [en|fr|es] to determine configuration for mirror list [en|fr|de...] Smarturpmi is a web application which caters to the same needs as EasyUrpmi, with the advantage that each mirror displays the timestamp of latest sync and availability of all mirrors is checked 3 times a day. It's available in 15 languages (even
including English!) and a GPL app, currently running on our webserver but available for everybody to install it on his webserver.

===Some not so related topics===
What bring interest in packaging extensions that are updated upstream? Well, they are packaged for the same reason that others rpms:
~- unified installation with others packages,
~- can be automated (i.e. if I have 200 computers, do I really update each of them by hand?)
~- unified interface, ie, no need to search on 3 or 4 differents websites or software
~- installed systemwide and updated system wide
~- ability to know the version, and to ensure a known good version is used
~- checked by packagers (i.e. it should work with the distro browser)
If "there is update on upstream" is sufficient to not package something, then we shouldn't package anything ...

Valid XHTML :: Valid CSS: :: Powered by WikkaWiki