-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Is building from git really that much harder? Yes, it takes a > little bit of tweaking to get your configure flags right and > getting all the right dev versions of the dependencies installed, > but at least on Debian/Ubuntu (since you mentioned apt) you have > the quick shortcut of doing: > > apt-get build-dep php5 > > which installs everything you should need to build it. > > I usually keep a little "cn" script around which is just a saved > config.nice that I hack on when I am testing stuff. You can see a > slightly simplified version of the one I use for 5.5 here: > > http://lerdorf.com/cn.txt > > If you don't have a checkout of the tree already, do: > > git clone -b PHP-5.5 git://git.php.net/php-src.git > > Not that this actually checks out all the branches, but puts you on > the 5.5 branch automatically. You can switch branches without > redownloading to test other versions. > > cd php-src ./buildconf ./cn make make install > > All done. To check updated versions, just cd into your php-src > directory and type: > > git pull ./buildconf ./cn make make install > > You may sometimes need to do a "make clean" and for minor changes > you can skip the builconf and configure and just make again and > hope the make dependency system works.
Nothing's wrong with that. With building in obs you just get a "clean room" build. You cannot forget to make clean, you won't get side effects of some optional library installed by some 3rd application or not, it's reproducible and shareable. It doesn't add anything if you don't need this. > > I realize this is slightly more complicated than an apt-get, but > pre-building packages that will work with all the combinations of > libraries and things out there is a PITA. Yes, building for arbitrary combinations by hand is not what everybody wants. When you build locally, you don't care and don't want to care about different setups which have to work with your procedure. You choose what suits you best. Packaging a git build with a well-known (inherited from last distribution) php build configuration may help early detection of issues that come up with exactly that set of tools and libraries. It's not fundamentally different from the manual procedure. The one thing apt-get/zypper saves is time. You eliminate the commit states which won't build at all, at least for the end users. Now they have more time to figure how they make their legacy code work with the newest git PHP and why their test suite fails out of sudden - be it new features/BC break or a real bug. - -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: l...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEIUfoACgkQCs1dsHJ/X7CGBQCfa/Xd9FmQdKZArVfHXDLd4Sbn WfIAn1pqyd8QAQRTnzKJnWPTGDUDF4Tg =qV0h -----END PGP SIGNATURE----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
