[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2018-02-28 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.22.28-1ubuntu3

---
gtk+3.0 (3.22.28-1ubuntu3) bionic; urgency=medium

  * debian/control.in, debian/libgtk-3-0.symbols, debian/rules:
- disable the MIR backend, it's unmaintained and the mir team
  confirmed they don't it since they talk wayland now.
  That removes the dependency of mir libraries (lp: #1701747)
  * debian/patches/no_content_hub.patch:
- removed, that was only needed to be able to build the mir backend

 -- Sebastien Bacher   Thu, 22 Feb 2018 16:00:01
+0100

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1701747

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2017-07-03 Thread Sebastien Bacher
right, as said libraries being used need to stay installed, you have remote 
share support in the filemanager even if you never use that, you have audio 
libraries installed even if you don't have a sound device, etc.
That said the GTK mir backend is unmaintained and we might decide to stop 
building it this cycle, which would resolve your immediate issue

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1701747

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2017-07-03 Thread Nazar Mokrynskyi
I just want to keep my system clean. I don't have ubuntu-desktop and
lots of standard packages and noticed these Mir-related packages but was
unable to remove them. Not a big deal in general, but still a number of
packages that will never be used.

Also installation ISO contains these packages and everyone downloads
something that will not be used in most if not all desktop setups.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1701747

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2017-07-03 Thread Sebastien Bacher
the libraries are tiny, why are they an issue for you? it's the way
linux binaries work, if you use symbols from a library it needs to be
installed. the library doesn't pull in the server though so it shouldn't
be an issue. you have a probably other libraries installed on your
system for similar reasons since that's something quite usual. Nautilus
for example leads to have libsmb installed for people who need to
connect to samba/windows remote share...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1701747

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2017-07-03 Thread Alan Griffiths
IMO this is a design issue in Mesa - it hard links to all the backends
enabled at build time. That also means, for example that a Mir based
system pulls in a bunch of X libraries. The same is true for Wayland. A
runtime dependency would be more satisfactory for everyone.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1701747

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2017-07-02 Thread Nazar Mokrynskyi
I have nothing against Mir itself, but why can't those packages be
optional dependencies?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1701747

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages

2017-07-02 Thread Daniel van Vugt
Thanks for that.

However Mir is still under active development and is supported in
Ubuntu. Mesa is central to that effort and possibly GTK is too. So Mesa
will be set to "Won't Fix" for now. And GTK might also follow.

** Project changed: mir => gtk+3.0 (Ubuntu)

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1701747

Title:
  Remove hard dependencies on libmir* in relevant packages

Status in gtk+3.0 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I think everyone will agree that Mir is not used by majority of users.
  So I don't understand why many packages have hard dependencies on libmir* 
packages. I don't want them in my system because I'll never user them.
  Make them optional, please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp