I make (B)LFS systems for "end-user" use.  When it comes to optional
dependencies, I tend to avoid their installation and maintenance
"expense" unless I can see a positive, direct benefit to the end-user
experience.

So far I've avoided the GObject Introspection package.  It's optional in
many of the BLFS packages.  I don't see the positive end-user benefit,
but I'm getting a vague impression it's an "up and coming" bit of glue
that may someday be essential.

So I'm wondering if it should "be on my radar" for integration into
the "base" if I end up restructuring/rebuilding this system.  Can
anybody give me information about the roadmap for GI use in "modern"
Linux systems?
-- 
Paul Rogers
[email protected]
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL
:-)

-- 
http://www.fastmail.com - mmm... Fastmail...

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

Reply via email to