Ok, I am ready to connect our private brand libexpat to the build now, any final objections ?
What was the concensus on the xmlwf program, did we want it in the tree or not ? Would it be useful to anybody or is it just a hackers-proof-of-concept thing ? Poul-Henning In message <[EMAIL PROTECTED]>, Poul-Henning Kam p writes: >phk 2002/10/04 04:20:19 PDT > > Modified files: > lib/libexpat Makefile > Added files: > lib/libexpat libbsdxml.3 > Log: > Ok, concensus was to install libexpat under a "private brandname", and after > some deliberation the name "libbsdxml" was chosen since it conveys the two > most important attributes: "Private to FreeBSD" and "XML". > > Add a skeleton man-page to give the credit and point for further > documentation. (If somebody wants to write a true mdoc manpage for > this I am sure both the eXpat people and I will be grateful). > > (Still not connected to the build) > > Revision Changes Path > 1.2 +22 -12 src/lib/libexpat/Makefile > 1.1 +59 -0 src/lib/libexpat/libbsdxml.3 (new) > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
