| 1 |
Hey, |
| 2 |
|
| 3 |
I'm re-proposing the tarball approach. When a stable release is made, a |
| 4 |
tarball of the tree would be taken (while removing all of the non-stable |
| 5 |
stuff and just keeping the arch keyworks if necessary..).. And then an |
| 6 |
overlay rsync for security updates would be created.. This ensures the |
| 7 |
long term survival of the release.. It also allows us to keep |
| 8 |
"distributing" very old release (we know how many shops still use |
| 9 |
redhat7 or even 6) without putting too much strain on the mirrors. |
| 10 |
|
| 11 |
|
| 12 |
On Sun, 2004-08-08 at 18:51 +0000, Kurt Lieber wrote: |
| 13 |
|
| 14 |
> 2) replacing the stable keywording stuff with stable profiling stuff |
| 15 |
|
| 16 |
Why do we need something as complex as profiling? And something that |
| 17 |
requires work from every maintainer |
| 18 |
|
| 19 |
> 3) adding a separate rsync module for the stable portage tree (or one for |
| 20 |
> each release of the stable portage tree) |
| 21 |
|
| 22 |
Rsync is expensive for servers.. lets keep it down to the minimum. Its |
| 23 |
much easier to get ftp/http mirrors than rsync... |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Olivier Crête |
| 28 |
tester@g.o |
| 29 |
Gentoo Developer |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives