This may be naive, but I would assume you would:
1) Download new source with fixes
2) Rebuild it with the same configuration options
3) Do a differential between the two trees, comparing:
a) the filenames, (to see if there are any missing or new files )
b) file checksums to identify which files changed and which didn't
4) Create a "patch" package, that updates the pkginfo, and contains the
affected files
Some issues and questions:
How are builds handled between 32/64bit and x86/sparc? How are builds
handled for the different sparc processor series? What determines if I need
to build 64-bit binaries? Would I be responsible for keeping track of
security alerts, or are there dedicated participants that monitor the
appropriate lists, and notify package maintainers if they need to take
action? What are the criteria for upgrading the binary to a new version of
the application?
I just realized something. I am being naive. Historically Sun has not
upreved the version of the application, but has backported "patches" into
the existing codebase. I am not sure whether or not, rebuilidng with new
source, or backporting fixes into "our" source is the correct way going
forward for this application.
-Brian
P.S. -
Brian,
any words on how do you plan to handle future [post-integration] patches ?
--
Regards,
Cyril
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
