| 1 |
On Thu, 2004-05-20 at 21:12, Markus Nigbur wrote: |
| 2 |
> Why do we distinguish between global and local useflags at all? Is there |
| 3 |
> a real difference between them? |
| 4 |
|
| 5 |
I say, just drop global useflags. |
| 6 |
While at it, drop global CFLAGS. |
| 7 |
Drop global it's silly. |
| 8 |
|
| 9 |
|
| 10 |
I think we need to go back to the basics: |
| 11 |
|
| 12 |
What does portage add that native installation doesn't? |
| 13 |
|
| 14 |
* Automatic non-interactive configuration sensitive dependency |
| 15 |
resolving. |
| 16 |
* Tracking of installed files for easy removing. |
| 17 |
* Gentoo integration. |
| 18 |
|
| 19 |
I don't know why useflags was introduced in the first place. But is it |
| 20 |
really the best sollution to provide the above? |
| 21 |
Can package configuration be stored in the package native format and |
| 22 |
still provide dependency data? |
| 23 |
|
| 24 |
|
| 25 |
I feel that we should try to move away from the monolithic nature of the |
| 26 |
portage tree and try to harness the power of "the web" more. To do that |
| 27 |
we have to push as much of the package handling as possible upstream. |
| 28 |
|
| 29 |
-John |
Archives