I created a set of ebuilds for the xfce4 beta1 released two days ago. I created three new categories for this, because it is IMHO the right way to do it, and it's the way gnome does it. Xfce evolved beyond "just another window manager", besides, it consists of more then 1 tarball / package nowadays :-)
Created attachment 12930 [details] Set of ebuilds
do u know what package installs libgladesupport.la, xffm fails because its missing
I figured it out...needed to change emake to make. thanks for submitting I had already made most of the builds, but I used alot of your stuff to fill in the gaps. This will be in portage shortly, but we opted not to make new categories just use existing.
You might want to add these dependencies to xfprint: app-text/a2ps apps-text/psutils devs told me these where needed for xfprint to work. I still can't get it to work, but might help some people allready ;-) (printing to a file and then feeding the file to lp does work btw)
Thanks, added.
hi Brad could you please add in beta2 --enable-xinerama in libxfcegui4? something like src_compile() { local myconf myconf="" use xinerama && myconf="--enable-xinerama" ./configure \ ${myconf} \ --disable-debug \ --host=${CHOST} \ --prefix=/usr \ --infodir=/usr/share/info \ --mandir=/usr/share/man || die "./configure failed" emake || die } Have you forgotten about xfce4-systray or am to silly to find? xfce4 is a very small package (compared to kde,..) and compiles fast. For cvs I had only 5 ebuilds (libxfce4util, libxfcegui4+libxfce4mcs, xfce-mcs-manager, the rest, the extras) and I never emerged one of them alone. Can there be a reason for example to emerge only xfce-mcs-plugins? btw I would prefer a portage-solution like kde or gnome where alle ebuilds are under one dir :-) thanx joe
adding xinerama now, and I've just been following the official beta releases...systray wasn't in beta1 neither was xfce4-themes iirc, but they should be in portage as I added them with the beta2 packages
