On Thu, 2008-09-25 at 10:13 -0400, Ken Mahoney wrote: > Good morning, > > There are a few binary objects that must be present under ~/libsrc > before SipX can be fully built. Among these are the java-sun-windows > JVM and Sun's JDK package. I believe these types of files should be > checked into the sipXecs repository. I was considering whether these > should be saved into the ~/src/lib/ directories and then have the lib > make infrastructure copy them over to ~/libsrc when a build begins. I > realize that traditionally ~/src/lib was preserved for packages that > affect SipX run-time only, but maybe it should be expanded to include > special packages like these? Or perhaps, a ~/src/buildpkgs directory > (or something similarly named) should be created for these types of > objects? >
I personally don't like stuff like this checked into source control. I don't like libs (jars) in source control either, but thats another battle. There was talk in another thread about looking at Apache Ivy for dependency control. I haven't looked at this too closely, but Maven (which I believe was the inspiration for Ivy) allows dependencies to be declared for build time, test time, run time, etc. This sort of facility would allow us to keep these tools/packages in a repository that we maintain, but that is separate from the source code. Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
