| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
|
| 5 |
On July 18, 2002 07:23 pm, Marko Mikulicic wrote: |
| 6 |
> However I doubt of the practical usefulness of a global peer-to-peer |
| 7 |
> solution. I have an 128bps upstream bandwidth and everyone going to |
| 8 |
> copy compiled kde-3.0 from me would compile it faster on PIII500 (~). |
| 9 |
> Since the userbase not so big as *pster and the number of combinations |
| 10 |
> of use flags is big, it is not very likely to find a package provided by |
| 11 |
> a fast host. |
| 12 |
> |
| 13 |
> I think it can be useful in a lan where, for whatever reasion, the |
| 14 |
> machines doesn't share the same use flag configuration. If a package |
| 15 |
> desn't use the "mysql" use-flag then it doesn't depend of having it or not. |
| 16 |
|
| 17 |
The peer-to-peer system would be interesting for the source package as well |
| 18 |
as the binary one. While one may claim that the use/cflags combination is |
| 19 |
too big, I, on the other side believe that the vast majority of the user are |
| 20 |
using quite similar flags. Also, the variation of the USE flags could be |
| 21 |
reduce if the USE file inside the /var/db/pkg folder only contained the one |
| 22 |
that was actually making a difference for the output of that package. |
| 23 |
|
| 24 |
- - -- |
| 25 |
|
| 26 |
Yannick Koehler |
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v1.0.6 (GNU/Linux) |
| 29 |
Comment: For info see http://www.gnupg.org |
| 30 |
|
| 31 |
iD8DBQE9OAjhfuKOJNEyL1URAmVNAJ4qtKuiws/WYUukKYJd6mkDzAEP2gCgoa3b |
| 32 |
KSUKnUzu42YNUBsw51ZqciM= |
| 33 |
=tEsB |
| 34 |
-----END PGP SIGNATURE----- |
Archives