* Darren J Moffat <[EMAIL PROTECTED]> [2008-06-13 15:25]: > Alan Coopersmith wrote: > > Jyri Virkki wrote: > >> Alan Coopersmith wrote: > >>> Since they're delivering these as SVR4 packages to the WOS in nv_92, > >>> they'd > >>> need to provide a list of packages needing this dependency to David Comay > >>> for his nv_92 distro-import updates, right? (I thought distro-import > >>> ignored the depends file in SVR4 packages and calculated it's own.) > >> Yes this is another of the difficult rough edges, we need to get to > >> the point where the engineers working on each component have a way to > >> specify the dependencies of their packages in the source/build itself, > >> not just by emailing David which won't scale (and is way too easy to > >> forget/get wrong).. David and I have talked about this in the past > >> but not sure when we'll get to that stage. > > > > Yeah, I've wondered if it made sense to push the distro-import definitions > > for packages out to the consolidations delivering them and have them > > deliver SUNW0sfw-distro-import, SUNW0x-distro-import, etc to the Indiana > > dock - but I'm also not sure we'll be doing things this way long enough to > > make it worth setting up that infrastructure and updating all the > > consolidations. For now, I've just been mailing out the changes needed > > for X in each build. > > Personally I think if it is needed for anything around another 5 builds > it is worth doing the SUNW0 delivery method.
Why wouldn't the consolidations each directly giving corrective patches to the importer be easier (than setting up yet another SUNW0* bucket brigade)? I'm pretty sure that Mercurial will scale, even if David might not... - Stephen -- [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
