| 34 |
In fact, when removing any dependency of the meta-package, it gets |
In fact, when removing any dependency of the meta-package, it gets |
| 35 |
removed as well, and all other dependencies become *leaf packages* that |
removed as well, and all other dependencies become *leaf packages* that |
| 36 |
autoremove will try to remove from the system. This is usually not |
autoremove will try to remove from the system. This is usually not |
| 37 |
what the user wants, as she probably installed (or had it by default) |
what the users want, as they probably installed (or had it by default) |
| 38 |
the meta-package to have a "standard" environment, but doesn't want or |
the meta-package to have a "standard" environment, but don't want or |
| 39 |
need specific packages. |
need specific packages. |
| 40 |
|
|
| 41 |
With the current situation, the only solution is to specify as |
With the current situation, the only solution is to specify as |
| 42 |
*manually installed* the packages the user wants to keep on her system. |
*manually installed* the packages the users want to keep on their |
| 43 |
|
systems. |
| 44 |
|
|
| 45 |
This document thus tries to introduce a new mechanism for |
This document thus tries to introduce a new mechanism for |
| 46 |
meta-packages, which would be marked with **Meta-Package: yes** in the |
meta-packages, which would be marked with **Meta-Package: yes** in the |