| 1 |
Hi all |
| 2 |
|
| 3 |
I'm coming in a little late on this discussion .. but here a are a few suggestions ... |
| 4 |
|
| 5 |
Compile flags: |
| 6 |
|
| 7 |
people that want massive of fine tuning of compile flags for apss will more likely compile their own software, so I thinks it's safe to work only with arch settings. |
| 8 |
if you want the latest binary for mutt running on 486 you need file |
| 9 |
|
| 10 |
mutt-1.5.4.486.tar.gz |
| 11 |
|
| 12 |
for pentium |
| 13 |
|
| 14 |
mutt-1.5.4.586.tar.gz |
| 15 |
|
| 16 |
etc etc .. |
| 17 |
|
| 18 |
this is logical .. and workable. |
| 19 |
|
| 20 |
USE flags. |
| 21 |
|
| 22 |
This is a lot more tricky as use flags will effect alot of applications. |
| 23 |
|
| 24 |
I use vpopmail but without mysql ... |
| 25 |
|
| 26 |
This makes things alot more difficalt. using a default set of USE can cause problems and setups that people do not want, another way is using a meta system for chacking your USE settings against the USE settings used to compile the binary .. but that opens up many many "variations" on the binary systems and makes "maintance" hell, |
| 27 |
|
| 28 |
as to hosting the binaries ... maybe looking at something like bittorrent or other p2p system would be worthwhile looking into (this could even be investigated for the current rsync/distfiles system) but then hash/md5/etc checking would become very importand. |
| 29 |
|
| 30 |
just a few ideas .... tho I would probebly stick with compiling everyting myself ;P |
| 31 |
|
| 32 |
Henti |
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives