Thanks for your response. I will take your recommendation and get my feet wet on your second option. Then when that is complete I will make it a formal part of SFW.
I have just a few questions. If I check out the webstack from here ssh://anon at hg.opensolaris.org/hg/webstack/webstack-build As an anonymous user, will I be able to check my changes back in? And if not how can I get an account so I can? I have already registered on the opensolaris.org site if that will be sufficient. Also, I realize this is a dumb question, but what is the best way to test this? Which version of solaris should I use? The SXDE? -----Original Message----- From: Jyri Virkki [mailto:[email protected]] Sent: Monday, February 11, 2008 8:18 PM To: Lorenzen, James Cc: webstack-discuss at opensolaris.org Subject: Re: [webstack-discuss] How to create an IPS package for Hudson james.lorenzen at accenture.com wrote: > > What do I need to do to contribute Hudson as a package? > Is there some documentation about how to create a package? > > Keep in mind I have never used OpenSolaris, but I am a Linux user and > huge Hudson advocate. I am looking forward to the challenge and hearing > back from everyone. Welcome and thanks for the interest! If you'd like your package to eventually be a formal part of Nevada (which will automatically later make it a part of the core Indiana repository, albeit with delays), the current approach is to integrate it into the SFW[1] consolidation (consolidations are a single source tree agglomeration of many unrelated components that get built together; the various Web Stack components like Apache, PHP, Ruby, etc are all part of this SFW today). Some time ago I wrote a short summary (much detail ommitted, but I'll be happy to guide you through it once you get far enough) of what that involves: http://blogs.sun.com/jyrivirkki/entry/how_to_contribute_to_sfw The benefit of this approach is that once integrated, it will be automatically available as a first-class component in Nevada/Indiana which is nice. The drawbacks are that it'll take a long time (months) to get into a Nevada build that you (or anyone else) can actually download and whenever you fix a bug or make an enhancement it'll again take a long time before changes show up, so it's not at all an interactive experience. An additional pain point for you as the developer is that you'll need to build the SFW world as part of your development process, which takes several hours. An alternate possibility for you is to create a stand-alone repository for the component here on the Web Stack community and use a subset of the SFW build process to build it by itself. You can get this via: hg clone ssh://anon at hg.opensolaris.org/hg/webstack/webstack-build Once you have something working you could publish it so it is available for all of us. The benefit is that it's available right away and your feedback cycle is hours-days instead of weeks-months. The drawback is that users of the package must download the source and build it locally which isn't quite as convenient as having it on the DVD/repository. I'm working on finding a way to much more conveniently publish these packages as built binaries but can't promise a timeframe. My recommendation is to start with the simple build system at hg clone ssh://anon at hg.opensolaris.org/hg/webstack/webstack-build and make it work with the component you're considering. Since it is essentially the same build system for both the choices I described, that will be a valuable experience no matter which fork of the road you take later on, but at least you can experiment without having to build all of SFW. This is experimental so inevitably you'll run into problems, just let me know on the list and we'll address them as needed.. [1] http://www.opensolaris.org/os/project/sfwnv/ -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
