Re: [PHP4BETA] cvs: /php4 buildconf makedist

> 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? Simply put an automake -ac in makedist and voila. > > 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. -- Regards, Sascha Schumann Consultant