Moinak Ghosh wrote: > On Tue, Sep 16, 2008 at 8:43 PM, Alan Coopersmith > <[EMAIL PROTECTED]> wrote: >> Moinak Ghosh wrote: >>> *) Why tie every package version into an ON build number. What sense >>> it makes to refer to an ON build number for say Thunderbird ? >> None, which is why Thunderbird has the build number of the JDS build that >> produced it. Of course, since we build all the consolidations in sync >> around the same biweekly Nevada schedule to produce the Nevada & Indiana >> distros, JDS & ON build numbers are both really just the Nevada WOS build >> number. This has nothing to do with packaging and is all about our >> process for building our distro. > > I understand that, been there done that. You mentioned the requirement of > the > main distro. What if you want to have multiple deliverables, > distros or specialized > appliance images delivered out of the same repo. Won't it be nice > to have a way > to tying package revisions to releases of those as well. A separate > tagset will > make that possible, instead of this: > > pkg:/[EMAIL PROTECTED],5.11-0.97:20080905T010753Z
For those of us not familiar with your particular delivery model, can you give specific examples and explanations. In particular, I'm curious as to what you mean by "separate tagset". Most of your concerns seem a bit premature given that it has been said over and over that the existing packaging and build numbering will be refactored at some later date. Most of what you see in the packages today is an artefact of Sun's internal build process, from what I understand, not some secret desire to complicate your life :-) -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
