| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 11/08/15 03:13 PM, Gregory Woodbury wrote: |
| 5 |
> Is a possible solution something like an eselect module to |
| 6 |
> indicate the preferred interface kit? It could default to any |
| 7 |
> package that is available with a sequential set of preferred |
| 8 |
> order. Then ebuild would consult the eselect module, and users |
| 9 |
> who care can select the kit they want, and users who don't |
| 10 |
> care/know get the default. |
| 11 |
> |
| 12 |
> |
| 13 |
> Just a nickel's worth opinion. Due to inflation it isn't 2 cents |
| 14 |
> any more. |
| 15 |
> |
| 16 |
|
| 17 |
Firstly, that's what USE flags are supposed to be for in the first |
| 18 |
place. |
| 19 |
|
| 20 |
Secondly, although something could be done within phase functions to |
| 21 |
deal with whatever the eselected iface-kit is, that afaik isn't |
| 22 |
something that would be permitted in global scope and so RDEPEND |
| 23 |
wouldn't be changed. Also I forsee major issues with binary |
| 24 |
packages, as right now the use flag settings partly determine |
| 25 |
whether a binpkg can be applied on another system based on that |
| 26 |
system's profile/use-flag settings (and those would now be gone). |
| 27 |
|
| 28 |
If you're talking instead about using an eselect module to adjust or |
| 29 |
auto-fill /etc/portage/package.use ..... i dunno. I think the |
| 30 |
metadata setup to get that right is is still going to be a lot of |
| 31 |
work for dev's to do (meaning it won't be done). |
| 32 |
|
| 33 |
|
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v2 |
| 36 |
|
| 37 |
iF4EAREIAAYFAlXKUhwACgkQAJxUfCtlWe1WhQEAlpdOL975yR+jYyNQNZWKML6l |
| 38 |
ZJlKzxrEKM1JMfLs+acA/0ypsvc/DLULgZWqZY7t+KdbappPNlI/K6YJDPyeKtS7 |
| 39 |
=/9HJ |
| 40 |
-----END PGP SIGNATURE----- |
Archives