Am 01.12.2010 um 07:59 schrieb Douglas Hubler: > I pulled a "thread" so to speak when adding all the dependencies for > openacd and related support and refactored release engineering scripts > a bit. > > Highlights > * Use mock utility now instead of installing rpms after building. > Cannot say how amazing this tool is (thank you Russ H.!), almost as > amazing as it is slow the first time you warm the yum cache. mock is > also invaluable to testing rpm specs and dependencies before > production installation. Unfortunately rpm builds are order of > magnitude slower, but the benefits are worth it.
Could that be selectable ? What if I do not want to use mock ? > * lib/* projects got moved to ./* because location can be subjective > in the grand scheme of things (e.g. ./lib/sipx-openfire and > sipXopenfire). It also make things easier for release scripts And kills the idea of separating out all the dependencies into ONE git submodule instead of multiples > * all rpm build logic was removed from individual projects. This > should make supporting non-rpm distros cleaner nice, but how do we build rpms now ? > * larger binaries were removed from git and uploaded to > download.sipfoundry.org. Download of tars is seamless and can be > avoided by pre-downloading files. is there a make download command ? What does one do on a closed system to predownload ? > * freeswitch and openacd were added as git submodules which will make > upstream contributions to those projects a lot easier > * freeswitch spec, is very, very close to freeswitch's spec including > building of all modules. I'll try to position my minor changes to FS > upstream so all files can be identical. run a sed on build ? > * reduction of lines of code in release engineering scripts from 12K > to 3K and there is even more that can be dropped i haven't got around > to yet. The 3K includes new functionality like iso creation and > sipfoundry publishing and 6 or so new deps/projects. Over the years > the copy/pasting boilerplate code got out of hand. :) > * scripts much easier to maintain and add to > * ability to add new sipX project or dependency building with almost > effort by adding just one entry to top-level script. > * helpful targets like: > > make sipXivr.all-install... > which starts at project sipXivr and continues thru the list to the > last sipX project. This is useful when some target fails at a project > and you wish to pickup where you left off. The ellipsis will work for > most targets (e.g. sipXivr.rpm...) including lib targets. type "make > sipx.list" or "make lib.list" to see order. > > make list-missing-deps > which analyzes your distro and build requirements of all sipX spec > files and prints packages you're missing in a format that can be feed > to yum could they be also fed to the build system so it builds all the deps you are missing that are in tree ? > > make help > was there for a few weeks, but lists common targets and descriptive text. > > * Source-based installs default to run as user that is compiling. No > more SIPXPBXUSER=`whoami` as it's now the default. rpms are hardcoded > to run as "sipxchange" however as that is the only real value that > would ever work. nice > > There are still a few kinks, i'm still finding them, bare with me. I > will document this week. > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ Michal Bielicki Geschäftsführer / CEO Seventh Signal Ltd. & Co. KG Weigandufer 45, Büro 115, D-12059 Berlin Voice: +49 30 60988730 Amtsgericht Charlottenburg HRA 44413 B Ust.-ID: DE266981999 Geschäftsführer: Michal Bielicki Persönlich Haftende Gesellschafterin: Seventh Signal Ltd, 69 Great Hampton St. Birmingham, B18 6EW, GB, Company Nr.: 06889439 WWW.: http://www.seventhsignal.de _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
