Randy McMurchy wrote: > 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?
Excellent idea. Do it when you can. >> 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. Interesting. Spaces, tabs, and newlines in XML are all supposed to be equivalent. I'm not sure where the xml came from, but looking at the hal documentation in /usr/share/doc/hal-0.5.4/spec/hal-spec.html, they show examples with nested merge tags, but perhaps the whitespace between the <merge></merge> tags is significant. Would the following work? <merge key="storage.policy.default.mount_option.iocharset=[iocharset]" bool="true"/> Does the following fail? <merge key="storage.policy.default.mount_option.iocharset=[iocharset]" type="bool">true </merge> ------------------^ -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
