| 1 |
Hi all, |
| 2 |
I got this idea and I'm not sure if it would be feasible, but if it is, |
| 3 |
it could lead to many Cool Things: |
| 4 |
Is there any reason not to have dynamic libraries for most of the |
| 5 |
changes made by USE flags, that are used only if present, and then the |
| 6 |
USE flags would just specify whether to compile that library? |
| 7 |
|
| 8 |
That way, one of the benefits would be that USE flags could be changed |
| 9 |
on the fly, and the whole system could be tweaked with minimal |
| 10 |
recompilation... but probably the biggest benefit would be the |
| 11 |
programming paradigm shift that this could affect, by pushing the |
| 12 |
packages toward a more dynamic, client-server module where the different |
| 13 |
parts of the package have separate purposes that they each independently |
| 14 |
achieve. |
| 15 |
This way, it could also make development a lot easier. |
| 16 |
As an example, lets use some fictional package "quux" that has optional |
| 17 |
support for Kde or Gnome. |
| 18 |
the quux-kde library and the quux-gnome library could be interchangable, |
| 19 |
and, from the point of view of the quux-core code, the same, allowing |
| 20 |
one programming interface to apply to both. Changes to quux's main |
| 21 |
system would just be in quux-core, and quux-kde and -gnome could remain |
| 22 |
the same, while if gnome support needed improvement, it would just be a |
| 23 |
matter of improving the quux-gnome library, with no risk of breaking the |
| 24 |
main system or causing undesired results elsewhere. |
| 25 |
This would also allow for more shared code, because two packages could |
| 26 |
use the same library in some cases. |
| 27 |
|
| 28 |
So, what do you think? |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives