Date: Fri, 11 May 2007 02:10:05 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-hackers@freebsd.org Subject: Re: New FreeBSD package system (a.k.a. Daemon Package System (dps)) Message-ID: <f20c8u$htp$1@sea.gmane.org> In-Reply-To: <200705102105.27271.blackdragon@highveldmail.co.za> References: <200705102105.27271.blackdragon@highveldmail.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDB6EC1D000090CDB58D57677 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable David Naylor wrote: > Dear Jordan >=20 > Recently I stumbled across a document you wrote in 2001, entitled "Free= BSD=20 > installation and package tools, past, present and future". I find Free= BSD=20 > appealing and I would like to contribute it its success, and as your ar= ticle=20 > describes, the installation and packaging system is lacking. Since the= =20 > installation system is being tackled under a SoC project I am hoping to= give=20 > the packaging system a go. =20 I've just read the document, and since I was also thinking about the ports/packages system lately, here are a few random ideas: - I think it's time to give up on using BDB+directory tree full of text files for storing the installed packages database, and I propose all of this be replaced by a single SQLite database. SQLite is public domain (can be slurped into base system), embeddable, stores all data in a single file, lightweight, fast, and can be used to do fancy things such as reporting. The current pkg_info's behaviour that takes *noticable* *time* to generate 1 line of output per package is horrible in this day and age. And the upcoming X11/X.Org 7.2 with cca 400 packages (which is in itself horrible just for a X11 system) will make it unbearable (also portupgrade which already looks slower by the day). - A quick test confirms that the current bsdtar will happily ignore any extra data at the end of a tgz/tbz archive, so package metadata can be embedded there, thus conserving existing infrastructure and being fast to parse. I suggest encoding this metadata in a sane and easy to parse XML structure. I cannot currently actively participate in implementing proposed things, but I can give advice on sqlite, database and xml schemas if anyone wants to... --------------enigDB6EC1D000090CDB58D57677 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGQ7RdldnAQVacBcgRAsC5AJ9eOrtH/PZ1f0FCpUNCd5e8P0cepACgjJn1 4RDFx35acLcdnefjtDqgSEE= =/yM6 -----END PGP SIGNATURE----- --------------enigDB6EC1D000090CDB58D57677--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f20c8u$htp$1>