Re: Fwd: Bug#570579: xulrunner: please reconsider recommends for GNOME packages
Thangs for cc'ing the kde people. I'm not sure I have anything more to add,
but I do agree that packages that isn't expected to be $DE-only should not by
default isntall $DE specific packages.
On Friday 19 February 2010 22:35:35 Frans Pop wrote:
> Please follow up to the BR (#570579) if you have anything to add to it.
> ---------- Forwarded Message ----------
> Package: xulrunner
> Version: 126.96.36.199-2
> Severity: important
> Tags: d-i
> X-Debbugs-CC: firstname.lastname@example.org
> I was very surprised when I upgraded a KDE system to find that xulrunner
> tried to pull in all sorts of GNOME packages. It was quite a bit of work
> to unselect everything that got pulled in through those Recommends.
> I'm talking about the Recommends for:
> - libdbus-glib-1-2
> - libgconf2-4
> - libgnome2-0
> - libgnomeui-0
> - libgnomevfs2-0
> And the deps for those packages are far from trivial.
> I guess the change was introduced in 188.8.131.52-2 with:
> Merge xulrunner-1.9.1-gnome-support into xulrunner-1.9.1.
> But I question if the Recommends of those packages is policy compliant as
> Recommends should only be used for packages "that would be found together
> with this one in all but unusual installations" .
> And that's only true for systems running a GNOME desktop environment. For
> systems running KDE the GNOME packages are not needed and even in a lot of
> cases very much not desired.
> I also question the value of the Recommends: if a user is running GNOME
> they will all be installed already anyway!
> As Debian Installer now installs Recommends by default and the desktop
> tasks installs iceweasel for all desktops, this means that all those GNOME
> packages would get installed on KDE desktop systems by default,
> As iceweasel is supposed to be desktop environment independent, I urge you
> to reconsider this change. IMO the current Recommends make iceweasel
> unsuitable for default installation.
> I also feel that for packages like iceweasel integration support for
> specific desktop environments should always be optional.
> ps -------------------------------------------------------
I'm not able to telnet from a connection from the file menu inside Word XP,
how does it work?
From the control options menu within Outlook NT you must rename a attachment
on the BIOS display on the Ultra desktop for booting with a virus.