Hi Roger,

Roland Mainz, a community member who is doing the engineering work
for the ksh93 integration project, has some questions regarding this flag day.
I'm cc-ing Roland and the ksh93-integration-discuss at opensolaris.org 
mailing list.

Roland's workspace is currently based on build 37, but I will
be creating a workspace from the source on the current onnv-gate
and incorporating his changes.

Thanks,
        April

Roland's questions:

- Can I reuse the "mapfiles" generated from the *.spec files in the
  current build (B37) and simply rename them to "mapfile-vers" ?

- Do you expect any problems using the new scheme if the
  build machine is running build 37? 
  
- Would you be interested in reviewing the changes for the transition
  from *.spec to "mapfile-vers" ?

> Date: Tue, 08 Aug 2006 19:23:07 -0700 (PDT)
> From: "Roger A. Faulkner" 
> 
> The putback for the following bugid constitutes a flag day for
> practically everyone with a child of /ws/onnv-{gate|clone},
> but especially for user-level library developers:
> 
> 6357230 specfiles should be nuked
> 
> If all you have in your workspace is usr/src/{uts|psm|stand},
> you can ignore this message.
> 
> The change is large:
> 
> Contents Summary:
>      243   create
>      849   update
> Names Summary:
>     1725   renamed
> 
> The created files are almost all named 'mapfile-vers'.
> The updated files are almost all Makefiles.
> The deleted (renamed) files almost all come from the
> old 'spec' directories, all of which are now empty.
> 
> To maintain a reasonably clean workspace, you should do a
> 'make clobber' in usr/src before bringing over these changes.
> Nothing bad will happen if you don't do this, but you will be
> left with a lot of left-over cruft in your now-obsolete 'spec'
> directories which the new Makefile structure will not clean
> up for you with 'make clobber' (because nothing knows anything
> about spec files anymore).
> 
> One of the features of this putback is that there should be
> no change to any rebuilt executables or shared libraries.
> It is a massive no-op.
> 
> If you are working on a shared library and you have a change
> pending to any existing spec/*.spec file, or you have created
> a new spec/*.spec file, then you will have to recast your change
> to be a change to the corresponding newly-created mapfile-vers
> file.  All existing spec files will have been renamed into the
> deleted_files directory.
> 
> If your pending work includes the creation of a new library,
> together with its spec/*.spec files, you will have to eliminate
> the spec directory and create a common/mapfile-vers mapfile in
> its stead.  Your library will not build properly until you do
> this.  The Makefile structure no longer understands anything
> in your spec directory, and putting it back after this putback
> would be just wrong.
> 
> Take a look at these files:
>         /ws/onnv-gate/usr/src/usr/lib/README.Makefiles
>         /ws/onnv-gate/usr/src/usr/lib/README.mapfiles
> 
> If you need assistance transitioning your pending spec file
> work to mapfiles, send me e-mail for assistance.
> 
> Roger Faulkner
> roger.faulkner at sun dot com
> 
> 


Reply via email to