Hi,
On Tue, Feb 28, 2006, Filipus Klutiero wrote:
> Note that I disagree about policy being "*extremely* clear" about the
> importance of Recommends. Policy's definition relies on two relative
> terms, "strong" and "unusual". The only precise definition I can deduce
> from this is that a recommended package should be installed together
> with the package that recommends it in most cases. This means that
> synaptic *should* install the recommendations by default, but it's not a
> bug that it's not implemented (or cleanly implemented) yet. My answer
> was mainly triggered by the fact that this bug has an important
> severity, but as you didn't set the bug's severity after reassigning to
> synaptic, this might not have been your intention, so I might be arguing
> for nothing. Anyway, the bug is downgraded now.
The choice between the installation or not installation of Recommends
is left ultimately by the Policy in the user's hands, but that doesn't
leave the choice of supporting Recommends: or not at the level of
synaptic. Again, I strongly believe there's no doubt in the fact that
package managers MUST install Recommends by default (or it's a bug),
and MUST permit removal for uncommon situations.
The position you're taking of considering this lower priority is in
effect pushing package maintainers NOT to use Recommends because these
are simply not honored.
I don't care about the actual priority of the bug, it simply needs to
be fixed. And by soonish, I would hope prior to release, as this is an
important piece of the upgrade plan. I certainly don't consider it
wishlist though, and find it a bit insulting.
FYI, I've targetted the bug severity to be important (I'm not sure
whether the severity was at this level prior or after reassigning), and
I explained why (<[EMAIL PROTECTED]>, To:
[EMAIL PROTECTED]):
<<
I technically consider this to be RC because policy clearly defines how
important Recommends are, and it's clear how they should be handled,
however, given the following arguments, I understand that it's not RC,
and wish for prompt resolution of this problem which renders the
Recommends: field useless:
1/ the archive has lived until now with this problem
2/ the archive is cluttered of incorrect usage of Recommends instead of
Suggests
3/ this might not be trivial to implement for the next release
>>
Do we really want to allow a package manager which doesn't enforce
Recommends by default in our release, effectively putting its users in
an unusal situation (such as one requiring manual configuration) each
time a package without its Recommends is installed?
Cheers,
--
Loïc Minier <[EMAIL PROTECTED]>
Current Earth status: NOT DESTROYED
