Wow - That's terrific. I'm going through the following sequence just to get my bearings (Sorry if I'm being repetitive - Just want to make sure I set the context properly):
Understand how the Tomcat RPM was done - This means understanding how the Tomcat build file layout maps to the FHS file layout used in the JPackage RPM ... So I can understand how everything was linked using the new FHS file structure. - Understanding the updating process used for configuration files (Including jakarta daemon jsvc / unix wrapper / log rotate configuration configuration, etc.) - Run permissions / file ownership - Run level configuration / startup / shutdown scripts - etc. I want to get this into a nice clean little document. Bastiaan once this is done I'd love to get your ideas put inserted. Incidentally - Our rpm packaging mojo here: http://svn.apache.org/repos/asf/directory/trunks/daemon/plugin is different from this one right? http://mojo.codehaus.org/rpm-maven-plugin/pom.html I'm sending out an email suggesting that JPackage host one right after this mail. I think JPackage would be the logical home, since they are maintaining the FHS process around building the packages anyways.... Side note, just so everyone understands, JPackages are just RPMS built so that they fit the FHS standard. The JPackage group are doing this by hand / manually. They have a utilities rpm for helping with the shell scripting. Thoughts? OK - Back to documenting. Cheers, - Ole --- Alex Karasulu <[EMAIL PROTECTED]> wrote: > Ole, > > If you intend to use jpackage see if you can add the > functionality > straight into the daemon rpm here: > > http://svn.apache.org/repos/asf/directory/trunks/daemon/plugin > > Basically this daemon plugin is a dual purpose > plugin. It makes your > java app into a daemon on UNIX and a Windows Service > on windows > platforms using jakarta daemon jsvc and procrun > respectively. > > The neat thing about this plugin is that it does > that and generates > installers for your server application as well as > RPM packages. > > It's the RPM part we want to replace so it uses > jpackage instead of the > rpmbuild executable. That should be easy to do. > > Thanks, > Alex > > P.S. Bastiaan also had some ideas for improving this > plugin. Perhaps > you guys can work together on improving our > packaging/installer > generating plugin. > > Bastiaan Bakker wrote: > > On Tue, 2006-10-24 at 11:56 +0200, Emmanuel > Lecharny wrote: > >> Hi Bastiaan, > >> > >> I have created another JIRA, > >> > https://issues.apache.org/jira/browse/DIRSERVER-765, > which is related > >> to RPM creation using jpackage > (www.jpackage.org). > >> > > > > AH, great, a jpackage based RPM is even better. > > > >> Ole is trying to use it to create valid RPM. > >> > >> Feel free to add any comment to this JIRA, we > will use it to track any > >> progress on this task. > >> > > > > OK. > > > >> Emmanuel > >> > >> PS: can you use the dev list instead of sending > mails directly to me? > >> Some other committer may help you when I'm not > online ! > >> > > > > Heh, in your last comment on DIRSERVER-749 you > told me to contact you if > > needed, so I did... ;-) > > But I'll go back to the dev list for discussion on > 765. > > > > Bastiaan > > > > > >> On 10/24/06, Bastiaan Bakker > <[EMAIL PROTECTED]> wrote: > >> Hi Emmanuel, > >> > >> Now that ApacheDS 1.0 has been released > hopefully you have a > >> bit of time > >> again to go through the RPM packaging > patch in DIRSERVER-749 > >> with me. > >> When would be convienent? > >> > >> Regards, > >> > >> Bastiaan > >> > >> > >> > >> > >> > >> -- > >> Cordialement, > >> Emmanuel Lécharny > > > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
