Re: [PHP4BETA] cvs: /php4 buildconf makedist

On Sat, 17 Jul 1999, Sascha Schumann wrote: > > That would be doubling logic since we'd have to copy the entire buildconf > > logic to makedist, something that I don't think is a good idea. > > I don't follow you here. Is that your normal exaggeration? Having fun aren't we? > Simply put an automake -ac in makedist and voila. You want to call automake twice, once from buildconf and once from makedist? It might just be me, but considering there were exactly 5 revisions of automake in the last five years, I think you can handle deleting the symlinks once a year when you install a new version. > > > Thereby you avoid the copy process. `make dist' performs > > > a `cp -p' which automatically avoids the problem at all. > > > > Yes, but I like makedist better than make dist for official releases. I > > want to check that the release actually works after it's tarred and > > prepared from the tagged version on the repositories, not the other way > > around. > > I just wanted to emphasize the fundamental difference between the > two processes. And yes, you can test the tarball created by make > dist. You can cat it to your favorite device, rot13 and post it > to alt.harrybert. Great. I have better things to do with my time than check each release twice. If you want to do it, go ahead. I'm in favour of one, centralized distribution process, that doesn't have weird dependencies (you have to configure the distribution before you can create it?). make dist doesn't give you that, makedist does. Zeev -- ----------------------------------------------------- Zeev Suraski <zeev@zend.com> http://www.zend.com/ For a PGP public key, finger bourbon@netvision.net.il