On Fri, Sep 6, 2013 at 11:41 AM, Canek Peláez Valdés <can...@gmail.com> wrote: > On Fri, Sep 6, 2013 at 11:33 AM, Philip Webb <purs...@ca.inter.net> wrote: >> I just did 'emerge -pv digikam' for 3.3.0 >> & it wants to install 54 pkgs, incl systemd ; >> 10 pkgs are KDE & include Marble. >> >> Is my surprise justified ? > > Yes, I think it is. Probably gphoto2 pulls GNOME stuff, which in turn > pulls systemd. Support for gphoto2 in digikam is optional, I belive; > the easiest solution is to USE="-gphoto2". > > If you are willing to spend a little time investigating, I bet you can > install gphoto2 without systemd, but you need to see what is pulling > it. My bet would be PolicyKit. > > The thing is, GNOME 3 now need systemd. Therefore, a lot of GNOME > packages are setting their defaults dependencies to pull packages in > such a way that systemd is one of them. If you don't use GNOME, but > install one of its packages (or something that pulls something else > from GNOME), you can pull *by default* systemd. > > However, I'm pretty sure you can configure out systemd without too > much problem (if you don't use GNOME 3, that is).
I checked gphoto2, and I don't think is the one pulling systemd. In fact, I don't see any dependency of digikam as an obvious puller for it. Could you mask sys-apps/systemd and see what emerge prints when trying to install digikam again? It will tell you which dependency chain pulls it. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
