On 11/29/11 07:54 PM, Danek Duvall wrote:
Vladimir Marek wrote:
Hi,
I am incrementing version of a component in the Userland consolidation
and I am filling an RTI to get it integrated into the SRU gate.
Since this change only increments the version of the component,
I am looking for a definite answer on what to put into the list
of binary deliverables (its the "Binary Delivery" section in the RTI).
Seems like the SRU process needs some updating. The need for a "Binary
Delivery" section in a patch RTI made sense in the SVr4 patch days when a
patch was constructed out of just the files that were different from the
previous rev of the patch (or the original package), but all that work is
now done by the packaging system at upgrade time.
There is no more need for patch assembly -- the consolidation delivers the
built package to RE, and RE puts it in a repo, end of story.
Ok, does that mean that I don't have to put anything into the "Binary
Delivery" section?
Would it be just this kind of RTI (where I update the component
version), or any one going into SRU gate?
Tomas
Particularly for a consolidation like userland, where each component is
independent, and the build doesn't need to get crazy in order to make sure
that package versions are what they need to be. Regardless, that's not
your problem, but something for the gatekeeping staff to handle.
Danek
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
