On 10/12/05, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Funny you mention iso-codes.
>
> Apparently, Epiphany now requires it. And it is a PITA. Took me
> 15-20 minutes of googling till I found it was a Debian package and
> could download the damn thing.
No kidding. I was getting angrier by the minute.
> Then, it won't build because it requires PyXML, which is sort of
> a pain because it doesn't install the docs and I had to figure it
> out and do it manually (not that big a deal), but it isn't a CMMI
> package. You must do 'python setup.py {build,install}. Which means
> you must have Python installed.
Yeah, but by that point you probably have added Python as a dependency
for something. A python binding needed for BitTorrent is built in the
same way. Can't recall it right now.
> Oh, and did I mention that the iso-codes tarball (I used 0.48)
> doesn't come with a configure script? Instead you get to do
> a aclocal - autoconf - automake routine before you can run configure.
The one I found at debian had an autogen.sh script included. I ended
up using this one
http://ftp.debian.org/debian/pool/main/i/iso-codes/iso-codes_0.48-1.tar.gz
> Not very easy for the novice builder. I'm wondering if Epiphany
> is just too much a PITA for the book now. I had planned on posting
> separately about this. I still will. I'd like input if we need to
> add iso-codes and PyXML to BLFS just so we can build Epiphany
> without a ton of support questions.
Probably is too much of a PITA. That's quite BBLFS relative to the
current book. If it affects your decision, they're also dependencies
for totem. Not that that's in the book or anything.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
