Alexander R. Eremin wrote: > Only the lazy user did not compile a linux kernel independently. > However for linux there are conveniences like menuconfig (or xmenuconfig). > Why not to make similar things for solaris? It would be desirable to give the > chance > for the user to select easily from the menu to remove unneeded modules or > insert something else. > > Well. I hope I'm anything, but a lazy user..
There's two sides to the reason why there's no make menuconfig for Solaris 1) Currently the build is this big nasty WOS.. So you're talking about significantly changing a part of that in order to introduce a curses based interface. I've looked at, changed and completely torn apart the ON build system. (In fact it's sorry to say, but I could probably rewrite Makefile.master from scratch and don't need bldenv anymore.) 2) If you're really interested and evening will to change the ON build system you're going to fight changing 20 years of habits. I mean honestly ask any @Sun or ON dev how much they don't like changes to the build system. It's fragile to the point where even version bumping a compiler will give headaches. In reference to [1] I didn't read the whole thread, but I've been quietly working on this for the past 2 months. It has some peer review and most people that I've talked with about it seem very supportive. (I'm aware I'm probably duplicating some work since I've been told others are making spec files for ON.) Question about your original post.... Do you need to selectively compile different parts or selectively package? One can potentially speed up the build cycle where the other is designed to possibly reduce space.. (or maybe you need both?) Feel free to directly email. Cheers! ./C [1] http://mail.opensolaris.org/pipermail/tools-discuss/2007-November/007354.html (btw.. Alexander thanks for working on Milax... it was a great starting point for another part of my project..)
