From owner-freebsd-ports@FreeBSD.ORG Thu Sep 2 09:52:07 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D06F10656DC; Thu, 2 Sep 2010 09:52:07 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 170298FC08; Thu, 2 Sep 2010 09:52:05 +0000 (UTC) Received: by eyx24 with SMTP id 24so106621eyx.13 for ; Thu, 02 Sep 2010 02:52:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:date:from:to:cc :subject:message-id:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=edTFRQPn6sb6je5zSxwrLvhXmeiZGrb0MibMDB1byhk=; b=dO5gDTEOI34/XjnJX5tWdxqgeO5b6xEQWImRiDLdhq9v78dPir5HsI6mKg3fVRg60U O0tX+4QNXDgf823+7wrXlo+txSMSIKLEd0tvGHXK0h4lR+x71jek5ZlVfHM/41ozE278 OeOWYaA0L4rwQK40+5Udt3dxzhp9iO0T/Zslw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=gmax/lYEfC6ijM6b+Q4yjDA3cEVqAbiaa3Tp1+/5IM+0Ulzi0p80E/+/xDj9CdNd4Z ROEEosAL9n3Mflh4i0D5gCVYrKAsc8CP+xzTPrKoAP+QUUw7NvScjjz+Kzi/A+vgYymX imq4lQmS/CsoZ70M6yXWNhAbCSASntzZWZvmQ= Received: by 10.216.54.202 with SMTP id i52mr9140976wec.40.1283421124920; Thu, 02 Sep 2010 02:52:04 -0700 (PDT) Received: from azathoth.lan (stc92-3-82-245-249-89.fbx.proxad.net [82.245.249.89]) by mx.google.com with ESMTPS id e56sm166451wer.22.2010.09.02.02.52.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Sep 2010 02:52:04 -0700 (PDT) Sender: Baptiste Daroussin Date: Thu, 2 Sep 2010 11:52:19 +0200 From: Baptiste Daroussin To: David Forsythe Message-ID: <20100902095219.GA47247@azathoth.lan> References: <4C6DA0FA.7080203@DataIX.net> <20100820124332.GB1786@azathoth.lan> <86lj7o7e6e.fsf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Florent Thoumie , Julien Laffaye , Garrett Cooper , Tim Kientzle , Ivan Voras , freebsd-ports@freebsd.org, Anonymous Subject: Re: what next for the pkg_install rewrite X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Sep 2010 09:52:07 -0000 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 02, 2010 at 12:34:58AM -0700, David Forsythe wrote: > Eh, why didn't this thread spring up before summer of code got under > way (or during the many weeks it was running)? >=20 I was expecting for your reply :) Sorry I didn't launch this thread before that because I didn't get enough s= pare time before summer, nor during it. > Concerning the database situation, sqlite would be cool. If we can > ship the sqlite code either with libpkg or with the pkg_install tools, > it's a win (I don't read licenses, someone will have to tell me if we > can do that). Realistically, if this is doable, then there can be no > opposition because the pkg_install tools as they are now create their > own "database", so nothing is changing. Plus we'll get free > concurrency, which everybody wants. If I can get an okay on this, > I'll start reworking libpkg to handle it. sqlite if we goes on is BSD-like licensed so it should ne be a problem, it = is designed to be embeded (one .h and .c to compile) no need to import the full sqlite sources. (see www.fossil-scm.org from the author of sqlite). >=20 > The manifest format really does need to change. We should go with > JSON and either write our own specialized parser/writer or go with > something like yajl. Writing a parser and a writer that plug into my > libpkg will give you conversion tools (both forwards and backwards) > for free and adding properties and changing formats isn't really a big > deal because I store package information in a plist(5) (from OS X) > like structure. Bringing a fat library into base just for manifest > parsing will meet with resistance, so if you guys can find some really > small json lib (I'm talking 1 or 2 files) that's license compatible, > I'll happily suck it into libpkg. >=20 That would be great, the json lib I use for testing purpose cjson (http://sourceforge.net/projects/cjson/) which is really simple to use, BSD license and can be embeded. I have writen a pkg_register which is a quick a= nd dirty version of pkg_add -O just to be a dropin replacement of PKG_CMD for = ports to register new package with the new manifest (without the need of patching bsd.port.mk) > The lua stuff is way too far off in dream land for my taste... >=20 I think the only interest of lua in pkg_install would be to allow hooks wri= tten in lua but this is not very important in the state we are). So let's forget lua for the moment :) > The things that you guys want to drop from plists are things gcooper > has been wanting to get rid of and replace for a while, and libarchive > restoring group/mode/owner perms has been the plan for a while now I > believe (I actually just ignore this stuff in libpkg). >=20 > Separating ports and packages is silly, because they need to coexist. > Like gcooper pointed out, ports should be using the pkg tools to build > and install packages. Agree with that >=20 > The repository format is something that you guys didn't really touch > on that I think could use some fixing, but I'll wait to see where this > all goes and maybe throw some ideas on a wiki page later on. >=20 I expect for your ideas on the wiki page. > In the mean time, I'll keep building libpkg too work with the pkg > system in its current state. >=20 How hard would it be to add support for the new manifest on you libpkg whic= h is really great by the way :) How hard would it be to allow other developers to work with you on libpkg? separate the tasks etc. regards, bapt --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkx/c9MACgkQ8kTtMUmk6EyMQQCfZkG75FHsALwqIb/abCfzCuZG b9IAoKLvKOochgYQHqgGmMrnDu7ywNjv =H9QA -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--