From owner-freebsd-ports@FreeBSD.ORG Thu Mar 14 07:50:13 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E1C24FA0 for ; Thu, 14 Mar 2013 07:50:13 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id 7B8BD9C3 for ; Thu, 14 Mar 2013 07:50:13 +0000 (UTC) Received: by mail-bk0-f51.google.com with SMTP id ik5so854438bkc.38 for ; Thu, 14 Mar 2013 00:50:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=mahQ/Bu36XYbPfvLbRhVReVWThvI41S1HL7+lFUFQaw=; b=Ghg0PY2WatYfG+vJGtaNKaq6q8ih9faFoU3cxXaQbYrATrKWfdujF/zvzb7u4gDNbN skvpjafmk37bcnFPozTSP/o3z28vbtGELwD/Notv1GivYDMeKesxHgVgmQKjeGxPVgkZ 7GfLVSFO+IVNLVOfB6YNUCdAOur8J/D73nzFqKygMBwkUXKTbhyjdGFQIcXR3Dmg3Twk 3hrUd8FOqUEB6jUfkR0g9D1qPyJtRr/affDGodbIVlhdX4qLaS2QNF0mADr3Oiwv5AIG 5MK2P+OeqHIGa9QRq9Dv9PXHUDeY1F/JZzwbAcTpR9VFueti3AJVhU8nTR1zZ0dn1lHw uv8w== X-Received: by 10.205.4.70 with SMTP id ob6mr617886bkb.95.1363247412577; Thu, 14 Mar 2013 00:50:12 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPS id gi19sm341081bkc.2.2013.03.14.00.50.11 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 14 Mar 2013 00:50:11 -0700 (PDT) Sender: Baptiste Daroussin Date: Thu, 14 Mar 2013 08:50:09 +0100 From: Baptiste Daroussin To: Aristedes Maniatis Subject: Re: pkg MANIFEST documentation Message-ID: <20130314075009.GE53963@ithaqua.etoilebsd.net> References: <51417D87.8030901@ish.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fWddYNRDgTk9wQGZ" Content-Disposition: inline In-Reply-To: <51417D87.8030901@ish.com.au> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 07:50:13 -0000 --fWddYNRDgTk9wQGZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 14, 2013 at 06:34:31PM +1100, Aristedes Maniatis wrote: > I am trying to create a package without first having a port, but I'm find= ing it really hard. >=20 > Firstly, the pkg MANIFEST format isn't well documented. For example: That's on my TODO list to bring the documentation for MANIFEST into a compl= ete one >=20 > 1. What is the syntax of "deps" when I want to depend on Java, but not sp= ecify the version? I've tried this: >=20 > deps: > javavmwrapper: {origin: java/javavmwrapper} Here name and version are mandatory, this is to allow pkg add (used by the = ports tree, tinderbox and pointyhat) to be able to look at a package around the package you want to install when doing pkg add ./yourpkg.txz it will try to= get =2E/javawrapper-version.txz if exists. Compatibility needed. >=20 > but this is ignored with a warning. >=20 >=20 > 2. Everything under "files:" and "directories:" appears to have full path= s from root. If that is the case, how does the system adjust to a user's ow= n choice of prefix? And what is the point of the "prefix:" option earlier i= n the MANIFEST? >=20 > 3. I see packages with this syntax: >=20 > directories: > /var/db/something: y >=20 > What does the "y" mean? >=20 y =3D=3D try to delete while n =3D=3D to no try. meaning when pkg delete is called when it tries to remove the /var/db/somet= hing if it fails and 'y' was given then it will not output a warning. But if 'n'= was given then it will warn about it. >=20 >=20 > Secondly, I am confused by the tar packaging itself. It appears that my p= ackage only works if I build it using >=20 > tar Pf packge.tar / Why are you trying to pack using tar and not pkg create directly?=20 > =20 > Is the correct way to chroot to a folder, assemble all the files relative= to root and then tar in this way? Again, why doesn't pkg cope with relativ= e tar pathing? Isn't that the whole point of 'prefix'? Not at all package without prefix is broken by design because 90% of the binaries will have hardcoded prefix. To install respecting chroot just pkg = -c /mychroot/ install mypkg regards, Bapt --fWddYNRDgTk9wQGZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFBgTEACgkQ8kTtMUmk6EwYLwCgjE/QoSXNdNrOPOKu6Si2NQys 0GgAnRVHMEz0g0L+iC0jqBS2dY0LZKt9 =pmPd -----END PGP SIGNATURE----- --fWddYNRDgTk9wQGZ--