-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mar 12, 2005, at 12:08, Drake Wyrm wrote:
At 2005-03-08T15:16:56-0600, Brian Harring <[EMAIL PROTECTED]> wrote:On Tue, Mar 08, 2005 at 09:41:37AM -0500, Nicholas Jones wrote:the person that implements it (xml wouldn't be an issue).XML is an issue presently. XML requires C++, and we don't have that on the stage1 tarballs. Reviewing that restriction is on my todo list.Unless I'm on crack, xml.sax should be purely python based (batteries included approach)... So, the stage tarballs nuking xml is an issue, but it's not a dep issue afaik.
I've got a wild idea. How about if you just use a couple of flat files,
one for the users and one for the groups. For the users, each line would
contain the username, default UID and GID, maybe some comments, a
default home directory, and a default shell. That pretty much contains
all the basics you need for creating a user, and could be accurately
parsed by all kinds of simple tools, such as awk or grep. If you didn't
want to rely on other binaries or libraries, you could use the read
built-in and some shell magic to parse it. Simple!
My vote is for the XML end of things. This (as well as data interchange) is exactly what XML was built for, and it's never led me astray.
- --
Hasan Khalil
Ebuild/Porting Co-Lead
Gentoo for Mac OS X
PGP Key: 0x707B8F18 on pgp.mit.edu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin)
iD8DBQFCM0nFzsotBnB7jxgRAhTHAKCntCXlN8FBtlocJ7WP7Y0roSQI2gCgrWc1 obcN8IFzSuByhy4J3ur9OU0= =CLxa -----END PGP SIGNATURE-----
-- [email protected] mailing list
