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?
My concern in not having these types of files not saved in subversion is
that it leaves us at the mercy teams who release these types of
packages; source packages have been known to disappear from the Internet
as they approach the end of their software life-cycle, forcing
developers and end-users to grab the next available release of package
"X" hoping that it will still work with SipX.
>From a PV perspective, it is always easier/better to have a well-defined
base that doesn't wander over time. This reduces the amount of
regression and interop testing that needs to happen between releases.
Thoughts, opinions?
Thanks,
Ken
=====
Ken Mahoney
SCS Release Engineer
Nortel Desk: (613)
763-8499 Yahoo: mahoney_ken
3500 Carling Avenue ESN: (6) 393-8499
Google: mahoney_ken
Ottawa ON K2H 8E9 Cell: (613) 295-6140
Canada
Mail Stop: 04332C04
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
