Norm The current number of components currently within sfw keeps growing and appropriately the build time keeps growing as well. Now, when you migrate sfw to mercurial will you design the framework in such a way that one doesn't have to build every thing ? For example, if some one is interested in building a component, he / she will have to only check out its dependent components and the build will build only build those. Does that make sense to you ? If you need any engineering help, feel free to ping me. I can chime in after 1st week of June'09.
Currently, Jyri Virkki has designed a system for Web Stack (which tracks all web related components) where in one can check out lighttpd and it dependents without having to bother about PHP etc. It would be nice if such a similar or even better system can be designed for SFW. This should greatly enhance the productivity of lot of folks working on this project. thanks sriram Norm Jacobs wrote: > > C. Bergstr?m wrote: >> >> I'm sure this has been asked before, but please forgive me if I'm >> missing something obvious. Did sfwnw move to mercurial yet? When is >> this planned to happen if so? > No, SFW hasn't moved to mercurial yet, but it's in the works. *maybe* > around build 119. As part of the migration, we are going to split the > gate into two pieces. One piece will contain the source archives and > the other will contains the rest of the bits (build recipies, patches, > packaging, ...). The source archives currently comprise about 2.5 GB > of space in the gate and the rest of the bits are about 77MB. By > splitting this up, we will be able to keep the change sets to a > managible size. The changes that I integrated yesterday and the > changes that I am working on to unify the unpacking and patching part > of the build will help make this easier. > > -Norm > _______________________________________________ > sfwnv-discuss mailing list > sfwnv-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss
