Hello world,
After some discussion on the debconf list [0] it appears that policy
and current practice are in conflict, and that it's probably a good idea
to get this conflict resolved before debconf gets added to policy.
The conflict I'm referring to is from s2.3.8, Maintainer Scripts.
The firs
Excellent idea! I'd like to see this improved tasksel program.
and, if tasksel can accept some option to switch the topdomain
of the name space ("task-" part currently), then it can be used
some other meta package in different name space.
In <[EMAIL PROTECTED]>,
on Mon, 23 Oct 2000 08:15:07 -0
Hi
Ben Collins schrieb:
> Task packages can define different levels of installation. The
> tasksel program will follow these rules for each case:
>
> - Minimum, installs everything that the task-* package Depends on
> - Standard, installs everything in Minimum, plus packag
>
> Now, there are some related problems happening. One big one is the
> fact that "Recommends" and "Suggests" have lost their usefulness
> since apt-get came on the scene. I venture to suggest that several of
> the inappropriate task-* packages exist purely to remedy this. If,
> e.g., the Roxe
On Wed, Oct 18, 2000 at 01:05:28PM -0700, Chris Waters wrote:
>
> ~ $ grep-available -P roxen -sPackage|wc -l
>70
I think this is a different problem. There's no reason for every little
Roxen module to be a separate package.
Richard Braakman
5 matches
Mail list logo
