reflum, On Tue, 2011-01-04 at 23:37 +0100, Jonas Smedegaard wrote: > On Tue, Jan 04, 2011 at 11:21:24PM +0100, Philipp Schafft wrote: > >I added a debconf question asking if the package should be > configured. > > Choice is good, but not what this bug is about. > > This bug is about default behaviour. So only if default config (with or > without interacting with debconf!) is to _not_ enable DECnet, this bug > is not solved by that approach.
see bellow.
>
> >I'm not going to change the recommends to suggests as suggests is
> much
> >to weak and will affect other users ('why is my network net set up
> >correctly?').
>
> Users of DECnet obviously need DECnet configured by default. My
> proposal is not to change that.
This is what the package does currently. How I understand this is that
you want to relex this a bit.
> But users of DECnet should install the _tool_ to handle DECnet, not just
> install the _library_ and expect that to pull in the tool. That is
> simply the wrong way around, and cause this bugreport: Currently users
> of _any_ tool which _can_ support DECnet, gets DECnet enabled by
> default.
there is no 'the tool'. Can't follow you here. I just assume you talk
about dnet-common. If that is wrong please correct me.
dnet-common is just the package taking care about config. it does not
(really) include any tools at all!
dnet-progs in contrast includes some tools. Those are common to be used
with DECnet but not required for anything than there own functionalty (a
'leaf' package). (btw.: only about 10% (according to popcon) of DECnet
users have it installed!)
If you for example set up RoarAudio with DECnet support you just need
libdnet and a configured system (which is normally done by dnet-common).
There is no need for dnet-progs or any other package.
So what do you consider 'tool' here? any decnet enabled package could be
such a tool. Even ices2 could be.
I think we agree about libdnet's role in this game. It should just do
it's job and do not force configured network. This is done by both
Recommends and Suggests.
libdnet is the central and the only central package for DECnet support.
Above you said:
> Users of DECnet obviously need DECnet configured by default.
so how do differ?
Pollicy tells the following in '7.2 Binary Dependencies - Depends,
Recommends, Suggests, Enhances, Pre-Depends':
> Recommends
>
> This declares a strong, but not absolute, dependency.
>
> The Recommends field should list packages that would be found
> together with this one in all but unusual installations.
>
> Suggests
>
> This is used to declare that one package may be more useful
> with one or more others. Using this field tells the packaging
> system and the user that the listed packages are related to
> this one and can perhaps enhance its usefulness, but that
> installing this one without them is perfectly reasonable.
As libdnet is central package it is normally useless if system is not
configured. A configured network will not 'perhaps enhance its
usefulness' but without it it is normally useless.
So I understands this the way policy suggests us to use Recommends which
we currently do.
> No user of the _library_ should be surprised that it did not magically
> setup their network!
Nor should any user installing a DECnet using application be surprised
by not setting up network correctly.
If we drop from Recommends to Suggests it makes installing this
complicated and requires some document telling you how to setup, not
just apt-get install what you want like it is currently.
> Users of the tool should be unaffected by the change of the _libary_
> no
> longer pulling in the tool. After all, users of the tool should
> explicitly install the tool!
> I strongly believe that the simplest and most elegant approach to
> solving this bug is to lower the relationship of the _library_ with
> the
> _tool_ to only be a suggestion.
See above.
If you have any idea how to solve this in a way not affecting existing
or new users and helps with non-users but dependecy installing people
please tell me!
As I do not know how to find out automatically or do some good guess (or
any guess at all!) I think it is best to ask user if he/she/hir/it want
to do the full setup or skip it.
I would be happy to hear from you :)
--
Philipp.
(Rah of PH2)
signature.asc
Description: This is a digitally signed message part
