| 1 |
> After some experiencies with emerge, it could be great that to |
| 2 |
> do an emerge with USE interactive: |
| 3 |
> |
| 4 |
> $ emerge -I php |
| 5 |
> >>> ... |
| 6 |
> Use Java [Y/n]? |
| 7 |
> Use X[y/N] ? |
| 8 |
> .... |
| 9 |
|
| 10 |
This is an interesting idea, but can cause a lot of problems... It |
| 11 |
has potential after 2.1 is released, but I don't recommend doing |
| 12 |
things this way right now. |
| 13 |
|
| 14 |
If you merge applications without a specific flag for a dependent |
| 15 |
package, and then merge a package with that specific flag, it may |
| 16 |
very well assume that the support you requested is there. Little |
| 17 |
errors may creep up on you. While this should be fairly harmless, |
| 18 |
it might be a little annoying. |
| 19 |
|
| 20 |
Portage will gain a lot more support for SLOTS, USE, and keywords |
| 21 |
in the 2.1 series. It'll actually allow dependence based on a USE |
| 22 |
setting and the child's build settings. It will remember them for |
| 23 |
future emerges on a per-package basis as well. |
| 24 |
|
| 25 |
> I join the script, its name is emerge-interactive, this is in |
| 26 |
> fact the emerge script with my modifications (line 1840 to 1877) |
| 27 |
|
| 28 |
If you make modifications to portage, I'd really appreciate it if |
| 29 |
you would post patches on bugs.gentoo.org. It'll give me a chance |
| 30 |
to look the changes over and give feedback as well as consider it |
| 31 |
for integration into portage. (diff -u, greatly prefered) |
| 32 |
|
| 33 |
> This is my first gentoo and linux contribution so I'm waiting for |
| 34 |
> some feedback, impression, and sure critiques and amelioration |
| 35 |
> (this is the first time I script in python, so be indulgent !!) |
| 36 |
|
| 37 |
This one in particular I'd rather see as a front-end instead of a |
| 38 |
direct integration like this. Sticky flags (which will show up in |
| 39 |
2.1) will feed from the command line and will have a lot of rules |
| 40 |
regarding how use flags are set for a session. This method steps |
| 41 |
around portage's ability to determine Sticky (persistant, limited |
| 42 |
flags set for specific packages) flags. It might end up causing a |
| 43 |
lot of rebuilding due to global use flag changes. |
| 44 |
|
| 45 |
If you continue with integrating it, just make sure you follow the |
| 46 |
code changes that are coming up this summer, and perhaps it might |
| 47 |
be adopted in one form or another. |
| 48 |
|
| 49 |
--NJ |
Archives