On Fri, 30 Apr 2010 15:34:19 -0400, Sebastien Roy <[email protected]> wrote: > On 04/30/10 03:29 PM, Sebastien Roy wrote: >> A couple of minor questions: >> >> The spec file syntax is also conceptually an exported interface, and it >> needs a stability level. It would be nice if the spec file syntax were >> part of the materials (I'm guessing it's documented somewhere anyway). >>
The basic syntax is the same as rpmbuild spec files, and pkgbuild includes a set of predefined macros and supports some additional tags (attributes/keywords): http://pkgbuild.sourceforge.net/man.php >> How will the tools handle a hypothetical syntactic change in the spec >> file format? Is there versioning built-in to the format? >> I don't believe a versioning mechanism exists, but one could be constructed based on tags or macros. >> What kinds of source URLs are supported (e.g., http://, https://, >> file://, ftp://, all of the above?)? Does this deal with HTTP proxies? >> How? pkgtool invokes external wget for missing sources, so this is probably specified by wget. > > One more: > > Can a regular user with basic privileges use these commands to create > and publish packages? > pkgbuild doesn't need additional privileges to create SVR4 packages or use pkgsend (where restrictions would be dependent on the server). pkgtool is also aware of how to invoke pkgadd for SVR4 packages, and for that pkgadd assumes the "Software Installation" profile. -Albert _______________________________________________ opensolaris-arc mailing list [email protected]
