| 1 |
Excerpt from the official site: |
| 2 |
"BerliOS Developer is a free service to Open Source developers offering |
| 3 |
easy access to the best in CVS/SVN, mailing lists, bug tracking, message |
| 4 |
boards/forums, task management, site hosting, permanent file archival, |
| 5 |
full backups, and total web-based administration." |
| 6 |
|
| 7 |
To summarise the above sentence, it is a service similar to SourceForge. |
| 8 |
Although BerliOS currently has only three mirrors, this would most |
| 9 |
probably change as the number of projects hosted by BerliOS increases. |
| 10 |
|
| 11 |
As of writing this email, BerliOS is hosting 4842 projects. There are |
| 12 |
206(?) files being fetched from BerliOS by ebuilds in the tree. This was |
| 13 |
counted per ebuild, not per package. |
| 14 |
|
| 15 |
The proposed mirror name is 'berlios' and the three mirrors are: |
| 16 |
- http://download.berlios.de |
| 17 |
- http://download2.berlios.de |
| 18 |
- ftp://ftp.berlios.de/pub |
| 19 |
Something along the lines of mirror://berlios/${PN}/${P}.tar.bz2 can be |
| 20 |
used in SRC_URI. |
| 21 |
|
| 22 |
I'm sure all of you understand that not much work would be necessary for |
| 23 |
the the transition as it can occur over time, for example when package |
| 24 |
maintainers modify an ebuild. So, what do you folks think? |
| 25 |
|
| 26 |
-- |
| 27 |
David Shakaryan |
| 28 |
GnuPG Public Key: 0x4B8FE14B |
Archives