Date: Tue, 23 Dec 2014 15:10:16 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: Aristedes Maniatis <ari@ish.com.au>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: +MANIFEST changed syntax in pkg 1.4? Message-ID: <549985D8.5050804@FreeBSD.org> In-Reply-To: <54997D1B.30902@ish.com.au> References: <54978556.3010503@ish.com.au> <54997D1B.30902@ish.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TJbXrq6FBGSINxgHuaFhOc9hSS79Wi0AW Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 23/12/2014 14:32, Aristedes Maniatis wrote: >>> On 22/12/2014 02:43, Aristedes Maniatis wrote: >>> >>> Has the +MAINFEST file changed in sytnax from 1.3 to 1.4 and is now n= ot yaml? I notice that the +MANIFEST files inside packages already built = by the ports system look more like json in format. Where do I find docume= ntation for the new format? >=20 >=20 >> Matthew Seaman wrote: >=20 >> Yes, +MANIFEST is now generated using libucl -- which uses a JSON-like= format. I believe the differences between libucl and JSON are pretty min= or (something about comment syntax IIRC) so if you convert your setup to = use JSON, it should work. >> >> For more information about libucl, start here: >> >> https://github.com/vstakhov/libucl=20 >=20 >=20 > Thanks Matthew. Is there any documentation on the new format? I see not= hing is updated in the only docs I can find: >=20 > https://wiki.freebsd.org/pkgng#Package_format >=20 >=20 > I guess I'm really not understanding pkgng... I've used FreeBSD since v= ersion 4 but this is the first time I've seen something in the core syste= m so undocumented and with so many regressions compared to the previous t= ools. I really wish we could go back to pkg_ >=20 There's quite a lot of info in the README.md on Vslevod's libucl page on Github -- it's not comprehensive, but given you know the basics of YAML and JSON is should serve to get you going. The other advice I would suggest is simply to copy what has been done for other packages. Try: pkg info -R pkgname or pkg info -RF pkgname.txz which will give you a pretty-printed version of the +MANIFEST for any package on your machine, or any package tarball you happen to have. Certainly for installed packages this will produce the libucl style output even if the original input was in YAML style. Not sure about pkg tarballs -- it might even work there too. So you should be able to start with the +MANIFEST for an older version of your custom package and evolve it to match the latest package contents. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --TJbXrq6FBGSINxgHuaFhOc9hSS79Wi0AW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iQJ8BAEBCgBmBQJUmYXYXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT4CQQAIc9JJ52jkAF68Ycdw2o9YUE 2YYE9Xb4sdMkiqcMVwbnInHnE7/KNONvaK/87Mi4zFvkRXIForws1JIfo6h51BrU DpUkI7mQDkvtJSj1uMvI4GjDCXW6sDwL8yfsh28FRrKt9bV6hz/QdDyZRq30lcTh 7aClshWDMA7yfnzF+cS9t610FpcHsWmYyOCNslXXLKLqkeYNiOR2O9IA/6iJWzc4 DOblPCWL6MGRtKqM8eq6CS9kDQBB27qJUBxK+mCkghf2IezGeLM3iAFu4FlT5PP4 HS3TDS41Fx4A33nIGUAhtFCxOFCCi0o0RwrglfAZE+gK+62TsHeJ/k9ALjufM0/e zm1VFxa0FVo26VeXE/zmsyBgZ/6h/FQBW5fUtR/lbtHwvXSHmhqbiVQtvjksT3M3 vN5X7+ARqe2byg+euEnGDK+Cl4/tXpZ5QcoS508m4WPugrrNzjBmrqIqm1/4gwnv NUSPEIz7bw7WaTLH9KPfLUe8SmSsxJMEOYy68nBYDPl0RL/6u35VIyaxJ2xBSdjo gqUpHz9QXaG+MRNKHxOU8DU/22bQ1B0IC11PEblHBTDdMnoR4xtSnPr06qdIrvjW e/hCU0QGpN8A87tp0VcbZae1gsa11pADTHQRc2/5nVsbvhYy5FvkuF7YKdJEs4/0 3HWJt0IXl3IdYWlU+0x3 =4LOY -----END PGP SIGNATURE----- --TJbXrq6FBGSINxgHuaFhOc9hSS79Wi0AW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?549985D8.5050804>