1 |
I've been using Gentoo for a couple months now. Let me just say "I LOVE |
2 |
IT!" It is by far the fastest running Linux system I've had. I also |
3 |
love that it is typically pretty up-to-date on packages. I do have a |
4 |
couple concerns though. |
5 |
|
6 |
Hopefully my concerns have not been dealt with, and I just haven't |
7 |
realized how to do these things yet. |
8 |
Here's my list of suggestions: |
9 |
* A --use-flags on either emerge or qpkg. This would display which |
10 |
flags are used by a .ebuild. Then you can tell what things MAY be built |
11 |
into a package. (For instance, I probably DON'T need 10 programs to |
12 |
display AVIs.) |
13 |
* A simple way to do a per package enable/disable of certain USE flags |
14 |
when you build a program. (I like something like +avi -qt or something |
15 |
like that, but I don't think it would work with the way it is set up.) |
16 |
|
17 |
Perhaps a way to deal the second issue is a --interactive or --set-use |
18 |
flag on emerge. The way this would work is to display all the flags |
19 |
used by a package and their default values. Then give the user the |
20 |
option to change them for that particular package. You could then do |
21 |
this for each package you are emerging. (Note: this would take place |
22 |
after checking dependencies, but before ANY package gets emerged. You |
23 |
would do ALL these at the beginning.) I only see one real problem with |
24 |
this. If one sets a value to the non-default one and then emerges a new |
25 |
version of that package but does not set that value to the same value, |
26 |
this can lead to a difficult time hunting down what changed (as things |
27 |
may be broken). This could be remedied by storing the flags used within |
28 |
the /var/db/pkg region. This may also be useful for things that depend |
29 |
on another package but requires it to have something else built into |
30 |
it. (I hope that made some sense... at least the ability to understand |
31 |
what I'm thinking.) |