Re: [gentoo-dev] When does gnome-2.22 come in portage?

2008-03-13 Thread Patrick Ohearn
On Thu, 2008-03-13 at 18:02 +0800, Shaochun Wang wrote:
> Sorry for the impatience! Where is the gnome overlay?
> 
> -- 
> Shaochun Wang <[EMAIL PROTECTED]>
> 
> Jabber:   [EMAIL PROTECTED]

It's listed as gnome-experimental in layman.
-- 
Patrick Ohearn
Email: [EMAIL PROTECTED]
Jabber: [EMAIL PROTECTED]
Site: http://ge3k.net


signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] Introducing new lead for xfce herd and project.

2008-01-15 Thread Patrick Ohearn
On Tue, 15 Jan 2008, Peter Weller wrote: 

> Yay for dice! :D
> 
> On Wed, 2008-01-16 at 00:06 +0200, Samuli Suominen wrote:
> > Since dostrow is being retired or is retired, correct me if I'm wrong
> > we decided (actually we rolled dices :-) that welp is the new lead.
> > 
> > - drac

Congrats welp, so what are you plans as new overlord of the free world?

-- 
Patrick Ohearn
Email: [EMAIL PROTECTED]
Jabber: [EMAIL PROTECTED]
Site: http://ge3k.net


pgpw9Y5vyEO3L.pgp
Description: PGP signature


Re: [gentoo-dev] Project Update: qt-4

2007-12-20 Thread Patrick Ohearn

On Thu, 2007-12-20 at 09:37 -0500, Caleb Tennis wrote:
> > How about splitting qmake out to help with the WebKitGtk stuff, so we
> > don't have to dep on qt?
> 
> In theory it can be done very easily, because qmake doesn't rely on any Qt
> libraries.  However, it DOES rely on all sorts of .prf and configure time 
> option
> files that are installed to the file system.  But I'm hoping to get a very 
> minimal
> package together that will mitigate the need for a big Qt install for builing
> WebKitGtk, yes.
> 
> Caleb
> 
Cool, thanks for the information :).
-- 
Patrick Ohearn
Email: [EMAIL PROTECTED]
XMMP: [EMAIL PROTECTED]

-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-dev] Project Update: qt-4

2007-12-20 Thread Patrick Ohearn

On Thu, 2007-12-20 at 09:05 -0500, Caleb Tennis wrote:
> Just a quick update on the happens in the x11-libs/qt world, as I'm 
> introducing some
> changes that will probably affect people in the not-to-distant future.
> 
> Since Qt is starting to get rather, ahem, big, I've decided that with the
> introduction of version 4.4 it's a good time to try and split it down into 
> more
> manageable chunks.  I'm introducing a few new packages that are designed to 
> break
> out some of the major pieces into their own packages.  I present:
> 
> x11-libs/qt
> x11-libs/qt-dbus ( Breaking out into its own package )
> x11-libs/qt-phonon ( New for 4.4, a wrapper around various sound modules )
> x11-libs/qt-qt3support ( Breaking out into its own package )
> x11-libs/qt-webkit ( New for 4.4, Qt's integrated WebKit support )
> 
> There may be some more of these as time goes on and necessity/desire dictate.
> 
> The main motivation behind doing this is to make the package a little more
> manageable, in that it's not one huge monolithic package with a million use 
> flags
> dictating which modules get built.  This should make dependant package 
> maintenance
> nicer, as you can just depend on the necessary packages and not have to 
> resort to
> the built_with_use trickery that we all love so much.
> 
> As well, we gain in the same vein as the split KDE style packages, that 
> updates and
> security fixes don't require a recompilation of all of the non-affected 
> modules.
> 
> There are still lots of goodies that need to be tested.  I'm sure there are
> edge-case USE flag scenarios that may need to be accounted for, performance 
> tweaks
> to be made, and other things I haven't thought of.  If you're into bleeding 
> edge,
> I'd love to have you try out some of these new packages and see if you've got 
> any
> failures or ideas for making them better.
> 
> As usual, this stuff is all package.masked right now pending lots of tweaks 
> and
> changes in the short term.  My guess is that it will hit portage proper by 
> the end
> of 1Q2008.  Hopefully we can have it all happy by then.
> 
> Feel free to file any bug reports you can find or think of.  Patches are 
> especially
> encouraged.
> 
> Thanks,
> Caleb
> 
How about splitting qmake out to help with the WebKitGtk stuff, so we
don't have to dep on qt?

Or can't this be done as easy as the other parts?
-- 
Patrick Ohearn
Email: [EMAIL PROTECTED]
XMMP: [EMAIL PROTECTED]

-- 
[EMAIL PROTECTED] mailing list