[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: brasero requires gvfs



Doug <dmcgarrett@optonline.net> writes:

> On 09/02/2014 07:35 PM, Patrick Bartek wrote:
>> On Tue, 02 Sep 2014, Rob Owens wrote:
>>
>>> ----- Original Message -----
>>>> From: "Michael Biebl" <biebl@debian.org>
>>>>
>>>> Am 02.09.2014 22:18, schrieb Rob Owens:
>>>>> I removed the systemd package from my Jessie system, and it took
>>>>> brasero with it.  Brasero depends on gvfs, and gvfs has some
>>>>> trail of dependencies that leads to systemd.  I'm thinking that
>>>>> the gvfs dependency doesn't make sense for brasero, but I wanted
>>>>> to get input from this list before I file a bug against brasero.
>>>>>
>>>>> Can anybody think of a valid reason why brasero should depend on
>>>>> gvfs?
>>>> brasero depends on gvfs so it can detect removable media.
>>>> For a burning application this is pretty much essential.
>>>>
>>> Ah, I was thinking about the SMB:// features and things like that.  I
>>> didn't realize gvfs was used to detect removable media.
>> Also, brasero is a GNOME app.  So, it's going to have GNOME dependencies
>> to work properly.  If you're using the default XFCE desktop with Jessie,
>> why not try XFCE's xfburn instead.  On my GNOME-free (Openbox only)
>> Wheezy system, I use it. Runs fine for what little burning I do.
>>
>> B
>>
>>
> It didn't need systemd before, so why should it need it now?

Debian has decided to feature several init systems, so any dependency on
an init system you're not using because you're using another one is a
bug that needs to be reported and fixed.


-- 
Knowledge is volatile and fluid.  Software is power.


Reply to: