Bruce Dubbs wrote these words on 01/01/06 21:26 CST:
> Randy McMurchy wrote:
>>So, my argument being that if you make Pyrex a recommended dep, then
>>you need to make GNOME-Python recommended as well. There is no
>>difference. They both provide the same functionality. Are you
>>willing to go there?
>
> Your arguments are reasonable. Lets leave it at optional. However, I
> still think we need to add the package to the book.
I have a thought, something you and the rest of the group can
consider. Currently in the book is already the PyXML package
(which, BTW, is not required any longer). We could change the
name of that page to "Python Bindings", add the Pyrex and
whatever Python bindings packages then come into play as time
goes on.
This wouldn't add an additional package, keeps the PyXML package
and adds Pyrex, Could even perhaps stick the instructions and
that big dependency list of GNOME-Python there.
What do you say?
> OK. PLease put it on anduin in a place Justin can get it.
I'll do that.
> Yeah, lets remove it. It is xml and the line breaks are not
> significant.
Okay, I'll ditch it. For technical accuracy however, note that
the locations of the line breaks *are* important somehow to
HAL parsing the files. Note this snippet:
<merge
key="storage.policy.default.mount_option.iocharset=[iocharset]"
type="bool">true</merge>
HAL parses this just fine. Now, move the closing </merge> tag
(which I think is more readable):
<merge
key="storage.policy.default.mount_option.iocharset=[iocharset]"
type="bool">true
</merge>
And HAL doesn't parse this correctly. I found this somewhat odd.
--
Randy
rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
07:17:00 up 99 days, 16:41, 3 users, load average: 1.00, 1.02, 0.73
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
