On Wed, 2010-05-05 at 17:25 +0100, Ken Moffat wrote:
>  OK, I've dug out my notes from last october, but all those say is that
> the new version didn't seem to be properly released and was only in
> fedora (fc12).  Looking at fedora cvs, it was a git pull from 20090913
> and according to them depended on pam, eggdbus,
> gobject-introspection, console-kit.  I've already expressed my
> reluctance to touch pam, with the old policykit that isn't necessary
> (there is a patch!).

That makes sense, if polkit was still pre-release at the time. Fedora do
tend to be ahead of everyone else on these sorts of things, since
they're largely developed by Redhat engineers.

As to PAM, I've never tried building polkit without it - didn't even
think of it as a dependency, since I just build it during LFS. But
looking at current polkit, it *appears* to support Shadow as an
alternative to PAM.

As to ConsoleKit, the dependency is actually the other way around - CK
depends on PK at build time - though I don't understand how they
interact at run-time. CK can also use PAM as a mechanism for recognising
when a user session has begun, but that's not mandatory either - their
preference is for apps like gdm / kdm to support CK themselves. I don't
know what the approach would be if you start X manually from the
console...

>  If I have time, I'll take another look now that it is properly released
> and used by more distros.  I've certainly got to add -introspection to
> what I build for 2.30.

Yeah, the introspection stuff has been a bit of a pain over the last few
Gnome releases, with some packages requiring introspection data that's
not produced by any other (requiring the gir-repository package as a
substitute). Mostly fixed for 2.30 though, now that packages like gtk+
provide their own introspection data. Hopefully the next step will be to
merge gobject-introspection into glib, where it belongs...

If you're unfamiliar with what all this introspection stuff is for, by
the way, it's essentially a change in how language bindings will work.
By having each package provide that data, it's no longer necessary to
write individual bindings from each language (Python, C++, etc) to each
of gtk+, gnome-*, Webkit, etc. Instead, each language needs just one
binding written to support all introspection-capable APIs. Sounds good
in theory, since it means language bindings won't be always struggling
to keep up...

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

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to