[oi-dev] package manifest "build" proposal follow-up

Guido Berhoerster gber at openindiana.org
Mon May 16 16:06:22 UTC 2011


Hi,

ary you aware that pkgbuild already produces source packages by
default and can provide the following metadata:

net.sourceforge.pkgbuild,version
build.tool
build.source_uri
info.maintainer_url
info.upstream_url
info.source_url
pkg.detailed_url

(see the description at
http://hub.opensolaris.org/bin/view/Community+Group+sw-porters/pkgcomp)

Here is an example of what the resulting IPS manifests look like
for the alpine packge from SFE:
http://staticdev.uk.openindiana.org:10002/manifest/0/SFEalpine%402.0%2C5.11-0.147%3A20110415T224822Z
http://staticdev.uk.openindiana.org:10002/manifest/0/SFEalpine%2Fsrc%402.0%2C5.11-0.147%3A20110415T224802Z

I suppose that covers already a large part of what you want, ie.
all required sources and infromation on the build tool and its
version are supplied and further information could be made
available though a web frontend or wiki page listed in
pkg.detailed_url. The CBE packages used for building the provided
packages could be supplied in the same repo which would only
leave SunStudio to be installed by hand.  Of course this would
only work for addon packages using specfiles, but for packges
which are part of a other consolidations such metadata would not
not make much sense anyway, e.g. cannot build a single package in
Illumos ON.
-- 
Guido Berhoerster




More information about the oi-dev mailing list