| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On July 18, 2002 09:39 am, Michael Cummings wrote: |
| 5 |
> then we could rename all the extensions to rpm and... |
| 6 |
> |
| 7 |
> sorry, not trying to be callous, but one flaw I would see is that there |
| 8 |
> is more to the flags than just the hardware flag. I have three machines |
| 9 |
> running gentoo, each of them with hardware in various states of |
| 10 |
> degredation. What you suggest would also require, in addition to a |
| 11 |
> package per hardware config, is one per possible config line (USE |
| 12 |
> variables can differ from user to user depending on their needs - i have |
| 13 |
> a box with a USE of -X -java -qt -gnome -kde -gtk just to insure that |
| 14 |
> nothing got put on that might have a dependancy on those), not to |
| 15 |
> mention dependancies (F begot G which begot H which begot I). For |
| 16 |
> instance, as time has progressed I have noticed that emerge -pu world |
| 17 |
> displays some packages marked as N, which means that new dependancies |
| 18 |
> have arisen since I fist installed the package in question. |
| 19 |
|
| 20 |
Well the idea was the following, If I build a package for my computer and |
| 21 |
could make other benefit from the fact that I've done so and someone maybe |
| 22 |
doing the exact same thing, so instead of having it re-compile the same |
| 23 |
things in the same way he could just pick up mine. If you do not have common |
| 24 |
system then you don't benefit from it but you don't lose anything. It is an |
| 25 |
addition not a removal. |
| 26 |
|
| 27 |
That's why I was putting talk about a peer-to-peer system. It would be nice |
| 28 |
that in some way, if want to emerge a build that has been emerged already on |
| 29 |
another system using the same configuration then you could at your choice |
| 30 |
decide not to re-do it but take the one that has been done. |
| 31 |
|
| 32 |
It does imply trust, security issues and all of this, but that is also true |
| 33 |
whenever you compile source code that you didn't investigate yourself anyway |
| 34 |
even thought there's a digest file, that file may have been created or |
| 35 |
modified on the mirror to make you download malicious source code. |
| 36 |
|
| 37 |
- -- |
| 38 |
|
| 39 |
Yannick Koehler |
| 40 |
-----BEGIN PGP SIGNATURE----- |
| 41 |
Version: GnuPG v1.0.6 (GNU/Linux) |
| 42 |
Comment: For info see http://www.gnupg.org |
| 43 |
|
| 44 |
iD8DBQE9NtRPfuKOJNEyL1URAriGAJ46+BN+prnnKwl+jeHwa06IohAB3ACgnFzv |
| 45 |
0Gqq6R2QwgIMQERhxWa7sI0= |
| 46 |
=G4Id |
| 47 |
-----END PGP SIGNATURE----- |
Archives