Re: brasero requires gvfs
----- Original Message -----
> From: "Patrick Bartek" <nemommxiv@gmail.com>
>
> 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.
>
Thanks for the suggestion. I use fluxbox, by the way. xfburn looks like it'll work. Personally I don't mind using command line for this type of thing, but I support/recommend systems of family and friends and they need a gui. cdw is a neat option for those too nerdy for a gui but not nerdy enough for command line.
xfburn is apparently aware that my cd drive is currently empty. Does anybody know what it uses to detect this? It is not using gvfs.
-Rob
Reply to: