| 1 |
> >One solution could be to extend ufed with a argument of a package. |
| 2 |
> >Ufed then only shows the relevant USE-flags and lets the user set them. |
| 3 |
> >Then ufed changes the /etc/portage/package.use accordingly. |
| 4 |
> Ignoring ufed for the moment, this brings up an interesting idea - is |
| 5 |
> there any reason portage couldn't dynamically manage the |
| 6 |
> /etc/portage/package.use file, so that: |
| 7 |
> |
| 8 |
> USE="foo -bar" emerge somepackage |
| 9 |
> |
| 10 |
> would add |
| 11 |
> |
| 12 |
> cat-name/somepackage foo -bar |
| 13 |
> |
| 14 |
> to package.use? That means a user could update packages and have them |
| 15 |
> installed the same way (unless, of course, I decided to specify a |
| 16 |
> differense USE= or changed package.mask). |
| 17 |
|
| 18 |
Actually, I wouldn't want emerge automatically adding local use-flags |
| 19 |
for a package that I might just want to try out a specific set of |
| 20 |
use-flags on. I would prefer to either have to manually add the flags in |
| 21 |
/etc/portage/package.use or have that functionality added to ufed as |
| 22 |
suggested... |
| 23 |
|
| 24 |
Patrick Börjesson |
| 25 |
|
| 26 |
-- |
| 27 |
Public key ID: 4C5AB0BF |
| 28 |
Public key available at wwwkeys.pgp.net |
Archives