[oi-dev] PROTO dir

[Bayard G. Bell]

Igor,

In either case we have to have manifest to determine what gets extracted
from the proto area and included in the package, so how does having a
single proto area make that problem any different? On the flip side, it
would seem easier to support something like sample-manifest if your
proto area is component-specific. It seems you want to trade that off by
satisfying dependencies via the proto area, but I'm not sure why that's
advantageous, particularly if I've got packages so I don't have to build
the dependency.

Maybe I'm missing something, but it would seem that having a mapping for
build dependency packages back to components that would allow building
of unavailable packages would be a better compromise.

Cheers,
Bayard

On Wed, 2011-11-09 at 01:09 +0400, Igor Kozhukhov wrote:
> Hello All,
> 
> I have idea - install all components to PROTO area in root - such as
> illumos-gate - and modify build system for using this PROTO in components
> builds.
> 
> This idea in - pre-build dependencies before final components and use one
> PROTO for builds instead of additional PROTO_DIR for every component.
> 
> We can generate IPS packages from ONE PROTO by using manifests - such as
> illumos-gate.
> 
> Best regards,
> Igor