> > > 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.
Not entirely true, idr-create needs list of binaries you deliver. It was
my first reaction - this is wrong thing to do. But, since pkg has no api
to work with repositories (so that we could gmake publish and then
change the repository so that it's IDR) and since userland can't build
IDRs by any other means, idr-create is the best thing we have at the
moment.
> 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.
--
Vlad
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
