Date: Wed, 2 Oct 2002 11:02:12 +0200 From: Marc Recht <marc@informatik.uni-bremen.de> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: expat2 in the base system? Message-ID: <20021002110212.43012b5a.marc@informatik.uni-bremen.de> In-Reply-To: <84545.1033548356@critter.freebsd.dk> References: <20021002103007.588d3bf3.marc@informatik.uni-bremen.de> <84545.1033548356@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
--=.Ph4c+pTOw7n3BD Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Rather than write another monster filled with weird structs and enums > I decided that ASCII is very extensible, and putting XML structure > on top of it meant that readily available libraries and tools could > work on it. Yes, it's IMHO the best way to do it. > And in fact, I have every reason to believe that it takes less code > in the kernel to construct XML with sbuf's than it takes to pack > everything in and out in a way which is properly versioned and all > that hair. > > So, I need an XML parser in the userland side of things. No, that it's there maybe other tools could (slowly) start using it. > (NB: XML flows from the kernel to userland, not the other way!) Maybe sometime.. :-) [...] > I've sent many emails to try to get peoples attention to this subject, > but nobody has really expressed much of an interest, but maybe now > that it is a more tangible issue that will change. I didn't see any message. After your commit, I made a quick glance through my archives current@, hackers@ and arch@ ... > I have not connected libexpat and xmlwf to the build yet, so nobody > will be screwed in any way until we do so. > > There are two ways this can be done, and I don't really have a > preference: > > 1. Under the name libexpat, in full flying colours. This means that > we are obligated to track the official libexpat rather closely > and ports will use the in-tree version instead of the ports version. I would go/vote for that. If it's expat then call it expat. Everything else is confusing.. [..] > Remembering the perl fiasco[*], I have tried for quite some time > to see if anybody had any good input on this, and nothing very > conclusional has emerged from any corner. In any ml? > I don't plan to commit the next stuff which depends on the existance > of this library this for another couple of weeks, so this is your > chance to test it out: Here is the patch which connects libexpat > in the tree in fashion 1 above. Hmm, with 5.0R in about six weeks wouldn't it be good to build and install the library asap ? > Let me know how much it breaks. We'll see. I've some stuff which depends on expat2 (python, apache2, ..) But: No risk - no fun. -:) Marc --=.Ph4c+pTOw7n3BD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9mrYU7YQCetAaG3MRAiXEAJ4rKtGraknUZar7b5o5x++N17V+lQCfY2Ps bS6dDgXP3hhsTkR37N0tSno= =sm2e -----END PGP SIGNATURE----- --=.Ph4c+pTOw7n3BD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021002110212.43012b5a.marc>