Hello,

I created branch for holding version 4.4.2 and prepare trunk to hold version
4.6.1.

Also I found some spec files which I already ported (long time ago) and
forgot to commit them.
I'm sorry for this. It looks as well that sstudio 12 update 1 doesn't need
as much patches as predecessor,
so maybe some of these patches are useless.

And finished the rest of the core Xfce spec files.

Here is the list:
1.  xfce4-dev-tools
2. libxfce4util
3. xfconf
4. libxfcegui4,
   libxfce4menu,
   libexo
5. xfce4-panel
6. thunar
7. xfce4-settings,
   xfce4-session,
   xfdesktop,
   xfwm4,
   xfce-utils,
   xfce4-mixer,
   xfprint,
   xfce4-appfinder

Xfce terminal, mousepad and others are missing.

I will put notification about this on the web with instruction how to build
it.
I will try to send spec files to juicer (next weekend) after some cleanup.

&IPS gurus,

I found problem with icon's cache, which wasn't updated, so some icons
didn't work before reboot or manually executing:
gtk-update-icon-cache /usr/share/icons/hicolor (and others)    (which is
inside spec files in post installation actions)

Is there any way how to update icon cache from IPS?


&Hugh,
Let me know if you have any questions regarding Xfce spec files.

&Doug,
You have wrong email hooked in svn commits, so I got some spam about
undelivered emails ;-)

Cheers,
Petr Sobotka aka Pietro

2009/7/29 Laszlo (Laca) Peter <Laszlo.Peter at sun.com>

> No-one seems to be maintaining it anymore, so if you want, I can just
> give you write access.  You will first need to associate with the
> xfce project and send me your opensolaris user name.
>
> Laca
>
> On Tue, 2009-07-28 at 09:56 -0700, Hugh Coomes wrote:
> > Laca,
> >
> > OK.  What is the procedure for updating the spec files ?   I currently
> have spec files for
> > xfce 4.4.3, but not the current xfce release, 4.6.1.
> >
> > Hugh
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20090816/d1494230/attachment.html>

Reply via email to