On 04/02/10 10:43, Hyon Kim wrote:
> 
> Hi,
> 
> It looks that the scheme for excluding files in the proto area  from  
> package processing has been
> changed on ON.    I think  'tools/protocmp/exception_list.h' is related 
> to the scheme but I don't find
> how an entry can be added to the list.  It point to  
> /opt/onbld/etc/exception_list* which
> looks to be related to interface stuffs.
> 
> Am I looking at the right place?
> 
> -Hyon

(Anybody got thoughts on where this information belongs?  Maybe more
extensive comments in the exception lists themselves?)


Do not modify anything in usr/src/tools.

In $CODEMGR_WS/exception_lists, there are five packaging exceptions
files.  They are reasonably intuitively named, though minimally
commented.  So:

packaging.closed: Use this file for objects that are installed into the
proto area only during a closed build, but which are not packaged at
all, even in an internal only or nonredistributable package.  Note that
object that end up in the closed-bins tarball should not be listed here,
because they should be packaged as redistributable, or listed in packaging.

packaging.ihv: Don't bother with this file.  It's for gatekeeper builds,
not standard developer builds.  It keeps you from getting errors about
objects from the ihv workspaces.

packaging.open: You'll rarely use this file.  It's for objects that only
show up as unpackaged during an open-only build.  Which means that
they're produced by the open build, but packaged as internal or
nonredistributable.

packaging.cpiotranslate: This is annoying, but you might need to know
about it.  Basically, the new tool (validate_pkg) understands that, when
you exclude a directory, you're also excluding its contents.  The old
tool requires separate entries for the directory, and for each file
therein.  Since the onnv-gate build now only uses the old tool for bfu
archives, we have sequestered the entries here that fall into this
category.  The plan is to see how much pain is caused by keeping them
separately, and either continue doing so, or invest a bit of effort to
update protocmp code to understand directory-level exclusions.

packaging: Most everything goes here.  If it's produced by an open build
or is part of crypto or closed bins tarballs, but is not packaged at
all, put it here.

--Mark
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev

Reply via email to