Your message dated Sat, 2 Mar 2019 20:54:54 +0100
with message-id <[email protected]>
and subject line Re: Bug#244418: dpkg: would like to see user-config options
result in more packages to install
has caused the Debian Bug report #244418,
regarding dpkg: would like to see user-config options result in more packages
to install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
244418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=244418
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.10.18
Severity: wishlist
this may sound a little odd, and it can be achieved by simply splitting
packages up and creating meta-packages.
but i would like to see dependencies be optional and based on
configure-time user input.
for example.
debconf itself, the package, can have different front-ends.
however, if you check the debconf dependencies, no mention is made
that debconf with the KDE frontend selected requires libqt-perl.
or that it requires KDE, for that matter.
one way to achieve this is to create a new package debconf-frontend-kde,
which depends on debconf, kde and libqt-perl.
another way to achieve this is to make the installation of kde and
libqt-perl CONDITIONALLY DEPENDENT on the user selecting the debconf
option "frontend=kde".
just a thought.
l.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux highfield 2.4.23-1-686 #1 Sun Nov 30 20:51:10 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages dpkg depends on:
ii dselect 1.10.18 a user tool to manage Debian packa
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix
Hi!
On Sun, 2004-04-18 at 12:21:44 +0000, Luke Kenneth Casson Leighton wrote:
> Package: dpkg
> Version: 1.10.18
> Severity: wishlist
> this may sound a little odd, and it can be achieved by simply splitting
> packages up and creating meta-packages.
>
> but i would like to see dependencies be optional and based on
> configure-time user input.
>
> for example.
>
> debconf itself, the package, can have different front-ends.
>
> however, if you check the debconf dependencies, no mention is made
> that debconf with the KDE frontend selected requires libqt-perl.
>
> or that it requires KDE, for that matter.
>
> one way to achieve this is to create a new package debconf-frontend-kde,
> which depends on debconf, kde and libqt-perl.
>
> another way to achieve this is to make the installation of kde and
> libqt-perl CONDITIONALLY DEPENDENT on the user selecting the debconf
> option "frontend=kde".
I see the apparent appeal, but I think this is a bad idea. This would
also make frontends quite unhappy I think, and complicate things
substantially, as suddenly the solution they have found gets
invalidated mid air during the upgrade itself. Not to mention that
dpkg itself might be completely unable to fulfill this request if it
is not being invoked via some frontend with "download methods".
I think I'm thus going to decline this request, sorry!
Thanks,
Guillem
--- End Message ---
